On 12/30/05 17:39 Tilman Sauerbeck wrote:
Thus, the ports tree is more-or-less uniform. All ports advertise runtime dependencies except for those belonging to the c build chain. In the users eyes, these are 'do not touch' anyway. Furthermore, setup simply maintains a list of what is necessary to have a functional install, and those are only preselected (not forced).
This doesn't solve the issue w/ pkgconfig (which is a build time dependency, but it certainly doesn't belong to the c build chain).
True, the same could be said about findutils and sed: maybe they're not strictly needed but they're often used at build time. I had a deeper look at the current core collection: I consider most of the ports to be essential for a functional Linux setup. Personally I'd prefer to have all the GUI-related stuff in opt, since most of my installations are server related; my concept of 'do not touch' includes all the other core ports and goes a litlle beyond the mere toolchain. I understand this view is totally subjective, anyway as stated before this way is a lot easier for packagers since it provides a well-defined list of implicit dependencies that are available on a minimal (but not to the extreme) CRUX system. That said I think this adantage is valueable not only at CRUX installation time. Regards, Simone -- Simone Rota WEB : http://www.varlock.com Bergamo, Italy MAIL: sip@varlock.com