Is there a particular reason for the use of the complete kde packages in the ports tree rather than meta-ports? It seems to me that it would be preferable to handle these as meta-ports, to install the individual ports that package a single application or library. It is already done with ports such as kooka and lanbrowsing, so I assume that this behavior could be extended to other parts of the packages without negative effects.
It could have the benefit of allowing (a more obvious means of) specific choices of packages, more particular dependencies for packages depending on specific KDE applications or their kparts, and isolating potential build problems within smaller ports that would not necessarily prevent installation of others. Has this been considered before or am I missing some potential problems? Would it add too much complexity to the packaging? -- John Stewart _______________________________________________ kde-freebsd mailing list [email protected] http://freebsd.kde.org/mailman/listinfo/kde-freebsd
