Hi, Juergen! Juergen Daubert schrieb:
The dependencies of the core packages are not included in the core packages. That's CRUX' philosophy.
That's not correct. See [1] for the according CRUX rules. [1] http://crux.nu/Main/PortGuidelines#ntoc2
That was a sloppy phrase of mine, but I don't see much difference to [1]: [quote] # '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 * run-time dependencies from core which aren't dynamically linked in are not to be listed, either [quote off] I just ran some times into missing dependencies while fundling with core packages on partially installed systems. Another example is the "new" libarchive dependency of pkgutils Nikolai ran into... We have had this discussion already. An optional (default on after a fresh installation) warning about changed/ignored dependencies would at least give the user a reminder that he should check the dependencies manually. Johannes just explained (again)... what the system could have done automatically. Well, these are the little pits and traps with CRUX you need to know... -- Clemens Koller __________________________________ R&D Imaging Devices Anagramm GmbH Rupert-Mayer-Straße 45/1 Linhof Werksgelände D-81379 München Tel.089-741518-50 Fax 089-741518-19 http://www.anagramm-technology.com