Tavian Barnes wrote: > On 2 February 2011 01:10, David C. Rankin > <drankinatty@xxxxxxxxxxxxxxxxxx> wrote: >> On 02/01/2011 10:41 PM, David C. Rankin wrote: >>> (3) Lastly, if anybody has interest, please look over the PKGBUILDs and let me >>> know where I'm doing something stupid. I have done quite a bit of reading trying >>> to digest PKGBUILDs and how to apply them to a large project like Trinity. I >>> don't claim to be an expert on them, so I know there are places where they need >>> improving. Thanks. >> Just a note. In addition to the tqtinterface and trinity-arts, trinity-kdelibs >> PKGBUILD is now working and open for comment: >> >> http://www.3111skyline.com/dl/dt/trinity/arch/dev/kdelibs/PKGBUILD >> >> so far so good -- a little PKGBUILD knowledge... is a dangerous thing :P >> >> -- >> David C. Rankin, J.D.,P.E. >> > > I don't see why you need meta packages; groups should do fine. I > think the only reason that Arch's meta packages exist is to provide an > upgrade path from the pre-splitpkg KDE days. > Except that when you install a group, if a package gets added to the group later it will not be automatically installed when you upgrade. With a meta-package it will. Jerome -- mailto:jeberger@xxxxxxx http://jeberger.free.fr Jabber: jeberger@xxxxxxxxx
Attachment:
signature.asc
Description: OpenPGP digital signature
