CruxCon 2004 Results

These is just a rough overview of the ideas from CRUXCon 2004; expect this to be explained in further details later on. Feel free to ask in clc-devel if you're interested in getting more information on any of these points.

Short term (2.1, 1st quarter 2005)

• merge cvs
• contrib -> opt, new group in opt 'core' (?) to mark ISO packages
• merge CRUX and CLC websites (keep wiki)
• Add CLC headers to base and opt ports
• combined httpup collection as new 'contrib' see: https://lists.berlios.de/pipermail/clc-devel/2004-September/000601.html
• dropping unmaintained in favour of the new contrib
• prt-get and httpup -> ISO
• introduce "Alias" feature using a list included with prt-get
• Look into distributed revision control to enable non 686 architectures
• Define subprojects (ports, doc, website, installer) whenever there is a need to
• Make sure there is an upgrade path 2.0 -> 2.1
• Maintain a list of renamed packages to make updating safer
• let people know about Matt's updated ISOs :-)
• "java-config" / "open-gl" config; policies in the Wiki for these kind of ports
• Laying down a rough release schedule to coordinate binary ncompatible updates (e.g. tag a binary compatible change 2.1 already now, to allow people to test it if they don't mind recompiling some packages, but don't tag it 2.0; in this case, we'd also benefit from a better version control system)

Medium term

• Extend pkgutils to "pass through" attributes
• allow arbitrary attributes in the package database (e.g. aliases, lock)
• accept non 686 subprojects if they are CRUX compatible
• work on the installer: allow injecting further packages
• define index file for additional ISOs which can be used by the installer do provide an extended package selection during installation

Long term

• test binary packages using aliases and attributes