On 04/19/06 15:50 Johannes Winkelmann wrote:
Hi there,
Hi,
here's a short summary of what I thought was the new definition:
1. We list all runtime dependencies except for gcc (libstdc++) and glibc. 2. 'core' contains essential packages for a CRUX system, and our scripts and ports expect them programs provided by 'core' to be installed; this means that build dependencies provided by core are _not_ listed in the dependency header
The rationale behind this was that core contains libraries like openssl, or curl, which can cause major breakage when updated; therefore, the dependency information should be available to rebuild the dependency tree recursively.
[omitting second revision as it's an extention to this one]
[your alternative here]
While I agree it's very handy to have a complete dependency tree, for simplicity sake I'm for omitting core dependencies; actually I expect the core ports to be binary compatible at least for each CRUX release lifespan[1]. When this is not the case, I think the user is smart enough not to blindly update the system when he sees there's a core port update: either he knows the port is binary compatible[1], or he is aware than some recompilation could be needed (revdep and the like). Maybe I'm assuming too much, so I'm also fine with extending dependency info as in your proposal, but as my second choiche ;) Btw, I feel I've not stressed enough [1], to me this can really give more sense to the 'core' definition and help improve the quality of our small nice distro. Regards, Simone [1] we could also put this as a requirement for updates in core -- Simone Rota Bergamo, Italy - http://www.varlock.com