On Wednesday, 16. March 2005 06:42, John Stewart wrote: > Has this been considered before or am I missing > some potential problems? Would it add too much complexity to the > packaging?
The existing splits exist because (enough) people were complaining about some KDE modules having dependencies they were really unhappy about, mostly because of their size. For example lanbrowsing has a runtime dependency on samba, kuickshow depends in imlib (and thus, gtk) and kdeaddons as a complete module has quite an assortment of dependencies as well. Each of those ports does indeed add quite a bit of maintainance overhead though, especially for upgrades. That's why we stick with the default modules unless there's some actual reason not to. In fact, KDE 3.4 will have one of the separate ports, www/konqueror-nsplugins merged back into kdebase, since the reason for it to go separate - a dependency on openmotif - went away, and during its existence "Why don't I have a plugins section in the Configure Konqueror dialog?!" became a FAQ - something that IMHO demonstrates nicely that a case-by-case approach to monotlithic vs. modular packaging is the most sensible thing to do. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org
pgpuqwI4i8B9S.pgp
Description: PGP signature
_______________________________________________ kde-freebsd mailing list [email protected] http://freebsd.kde.org/mailman/listinfo/kde-freebsd
