On Saturday 15 January 2005 19:59, Dan Armak wrote: > In the interests of full disclosure, I should mention that there are > monolithic (old-style) 3.4.0_beta1 ebuilds there too, and you can even mix > the two kinds. But I'd really like to see everyone use the split ebuilds > :-)
As a KDE user, I can see the advantages of split ebuilds. I can sympathise with the problems they will create for the arch teams, but I think those can be overcome with time. But what about the disadvantages that these ebuilds cause users? At the moment, the problem with any meta-package is uninstalling it. emerge -C kde-3.2 doesn't remove KDE 3.2. Portage removes the meta-package itself, but none of the kdebase, kdelibs etc that the meta-package installed. Administrators have to go around and emerge -C the individual packages. That's fine with the monolithic ebuilds. But having to do this for 400+ ebuilds is unreasonable. It's a lot of work to do, and there's a significant risk of human error. Until stable Portage has the support for auto-uninstalling all these packages, I believe we shouldn't mark the split packages as stable on any arch. Just an opinion, Stu -- Stuart Herbert [EMAIL PROTECTED] Gentoo Developer http://www.gentoo.org/ http://stu.gnqs.org/diary/ GnuPG key id# F9AFC57C available from http://pgp.mit.edu Key fingerprint = 31FB 50D4 1F88 E227 F319 C549 0C2F 80BA F9AF C57C -- -- [email protected] mailing list
