22 Feb
2011
22 Feb
'11
6:16 p.m.
On 02/22/2011 11:53 AM, calvin morrison wrote:
why are we calling it kde3mod? that is pointless.
We are rebranding kde3 to Trinity. I don't think we should keep it the
same. that causes confusion.
I have started moving the PKGBUILDs to the AUR, which is fine. (the
independant ones not the entire tree) I can maintain them (seeing as
they do not change often, they are SVN builds.)
I think we need to just wait until 3.5.13 is out completely then
switch over. Its only a few months till then and there is much work
that needs to be done on 3.5.12.
Calvin
I agree,
The reason it is called kdemod3 is what Albert did was to just replace the kde
3.5.10 source with the Trinity 3.5.12 source and then run the kdemod3 master
build script to build it --> resulting in kdemod3 packages instead of trinity
packages.
To fix this, all we need to do is edit ~ 50 PKGBUILD scripts and simply change
the pkgname and remaining variables from kdemod3 to trinity. (a big sed call or
'perl -p -i -e s/kdemod3/trinity/g'. (monkey on the keyboard stuff)
I would also rather work through the 3.5.13 packages and then make the current
release available to Arch rather than pushing 3.5.12 out. But it really makes no
difference. I have setup all my PKGBUIDs to handle the update from either
kdemod3 or an existing trinity version. If 3.5.12 is good and works fine, it
would sure be better than the old 3.5.10 kdemod3 I'm running with broken cups
printing and broken sftp kio, etc.., etc...
I've got spare boxes to throw the 3.5.12 packages on, so I'll see how that
goes before I can really way in one way or the other on putting 3.5.12 up :)
--
David C. Rankin, J.D.,P.E.