On 12/29/05 12:27 Juergen Daubert wrote:
one outstanding point is still the question how to deal with dependencies for core and even opt ports. IIRC one result of CruxCon 2005 was, to handle that in the following way:
- All core/opt ports should list run-time dependencies - but not to glibc and gcc - no build-time dependencies
Maybe I'm a bit late for this note, anyway, after having used the new collection layout for a while, I feel a bit nostalgic regarding the previous base/opt division. To me x11, gtk, firefox etc are not exactly what I'd call core requirements for a CRUX setup (even if it's important to have them on the iso). An idea is to move the ports from the previous opt collection into the current opt, with some ex-base port too, thus obtaining a true core collection, that really represent things that should not be removed (ie by prt-get) and are not listed as dependencies for other ports since they're implied (pkgconfig?). Note that this will not impact end users at all.
- remove build-time deps like pkgconfig - define a list of core-core ports, which must be installed to build ports, or ... ?
This two points would be handled by the suggested core/opt separation.
- if we agree with the rules above, I'll add all the missing deps to the core ports. - it would be nice if we had a complete core/opt list. I'm volunteer for creating/maintaining such a list. To build them I need the output of 'mkdeplist /usr/ports/opt'.
I plan to setup (in a few days) a build machine to fully test core and opt ports for missing deps, broken urls, etc. I'll send you the list of found deps for opt on a stock opt+core setup. Regards, Simone -- Simone Rota WEB : http://www.varlock.com Bergamo, Italy MAIL: sip@varlock.com