Annvix:Tools/ports
|
This page contains content from the old Annvix.org wiki and has been moved here to preserve content. These pages have been retained for historical and nostalgic purposes only. |
Annvix Ports
Similar to FreeBSD's ports, Mandriva's contribs, and other similar repositories, Annvix's ports collection is a (slowly growing) collection of packages that are not part of the default Annvix main package base. These are "third-party" additions that extend the functionality of Annvix but also don't burden the development team with maintenance. Annvix ports are packages that may be of interest to very few and may also be maintained by individuals who are not necessarily part of the development team. Examples of ports packages include the joe, various DJB programs such as djbdns, and other small utilities like pine and tree.
More information on ports can be found on the Using Ports documentation.
The Subversion repository for the ports packages themselves can be viewed.
Obtaining the builder source
The source code for builder and the Annvix ports scripts can be obtained from:
Future Plans
Ports is still in it's infancy and was introduced in a semi-working state for 1.1-RELEASE. The version provided for 1.2-RELEASE is more robust than the previous version, but still isn't complete. The ports system in 2.0-RELEASE is quite a bit better (introducing support for status flags and using apt rather than urpmi). A short-list of features/changes that need to be done yet include the following:
- GPG-sign generated RPM packages and enforce urpmi's checking of the signatures upon package installation
- dependency-building; if package X requires package Y and package Y is in ports but not yet built, queue package X for building and build package Y first
- use sha1sum rather than md5sum for the manifests
The following changes need to be done to the ports system before it is completely viable. NOTE: ports is no way is holding back 1.1-RELEASE; it can be updated post-release if we fall short on time.
- Support multiple repositories
- Support repositories of cvs, rsync and possibly svn
- Do a code audit
- ensure that every port package has an archive.md5sum file or don't accept it
- integrate package signing into build process
Write docs on how to submit ports; for example:
- create tarball of spec/patches/archive.md5sum
- in tarball should be a manifest file of some sort (developer email, name, host system info, etc.)
- send email to dev ml or a specific email address (ports@ perhaps?)
- write a script to automate all of this?
