Conary is a distributed software management system for Linux distributions. It replaces traditional package management solutions (such as RPM and dpkg) with one designed to enable loose collaboration across the Internet. It enables sets of distributed and loosely connected repositories to define the components which are installed on a Linux system. Rather than having a full distribution come from a single vendor, it allows administrators and developers to branch a distribution, keeping the pieces which fit their environment while grabbing components from other repositories across the Internet.
The goal for A-A-P is to make it easy to locate, download, and install software. Additionally, it supports making changes to a program and managing different versions that exist in the world, making it useful both for users and for developers. It uses a recipe that is similar to a Makefile, but with many enhancements, such as integrated Python script support, support for Internet access, and version control. An IDE will be provided that integrates your favorite editor, debugger, and other tools.
moap is a Swiss army knife for project maintainers and developers. It aims to help in keeping you in the flow of maintaining, developing, and releasing. It automates whatever tasks can be automated. It allows you to parse DOAP files and submit releases, send release mails, create iCal files and RSS feeds, maintain version control ignore lists, check in based on the latest ChangeLog entry, and more.
Releaser is a set of scripts to automate and manage the tasks related to software package releases. It is designed to be modular and to make it easy to both select a particular set of actions associated with releases of a particular project (such as changelog generation, uploading of tarballs, posting announcements to mailing lists), and create new actions that integrate seamlessly into the process. Its status is still somewhat experimental, but the most basic functionality is there.
ControlTier is a set of tools and an automation framework for deploying and managing multi-tier Web applications (or any application stack). It orchestrates the deployment and updating of code, data, and content across multiple physical, virtual, or cloud-based servers or clusters. Multiple tools include a command dispatching framework, a self-service Web interface, a multi-purpose CMBD/inventory tool, and a reporting infrastructure. Tools can be used individually or as an integrated system for large scale use.
0release is a program to generate source and binary releases automatically. With minimal configuration, 0release will generate a source tarball release candidate, build it to create a binary archive, upload them to your Web server, check the uploads, and tag the release in GIT and update the version number. It can run unit-tests and custom actions, such as building documentation, etc. For Zero Install users, it can also upload a signed XML metadata file about the release, allowing these users to upgrade automatically. Releases are signed with your GPG key.
Cvs-Brancher establishes a tagged branch in a CVS module and schedules a merge and build to occur at a later date/time. It might be used to roll out Website changes at odd hours, such as posting a press release in time for the start of the business day on the east coast, or to roll out cfengine changes to a data center during the night, to minimize the impact of downtime.
The 64 Studio Platform Development Kit (PDK) is a version control system for GNU/Linux distributions, allowing the creation and management of many different projects, based on Debian and Ubuntu sources. PDK is written in Python, and the source code is well commented and contains documented examples.