Hi Slash, First of all, we'd appreciate if you could use a realname. It is written in the CLC maintainer guideline that this is a requirement for this job. On Sat, Sep 06, 2003 at 11:47:28 +0200, [slash] wrote:
I (and other italian crux users) think that isn't good to have two collection of contrib ports (1.1 and 1.2), because many crux users often upgrade the system by installing the new version of their packages then even if their system is marked "version 1.1" they have a system thet is upgraded like (or more than) a 1.2 ones. You should really take a deeper look at how CRUX and CLC works. CRUX updates sometimes involve changes which have an impact on the ports (Pkgfiles and footprints). The ports CLC provides for a specific version of CRUX will work for this version. If a new version of CRUX is released (let's say 1.3), CONTRIB-1_2 will continue to work for 1.2 systems even if 1.3 will use RPM. The more, dependencies of CLC do not include versions but imply that you use the current version of a dependency from the ports tree. Having no (CRUX release) version tags for CLC ports would break this system completely.
The CLC tag are important to match the library and software versions of the corresponding CRUX release, to make sure it works with the version of pkgutils of this release and to ensure the dependency specifications of CLC. Kind regards, Johannes -- Johannes Winkelmann mailto:jw@tks6.net Biel, Switzerland http://jw.tks6.net