Personal tools
     DOCUMENTATION

Conary:Packaging Process

From rPath Wiki

Jump to: navigation, search
Conary --> Packaging --> Packaging Process

Conary packaging follows a consistent process. After configuring a build environment, a packager can conduct packaging activities as needed in that environment, generally abiding by this process.

Though the process is consistent, there are two build tools available for cooking packages and groups: Conary and rMake. Conary uses the local filesystem as it is when building. rMake uses the build requirements of the package or group to set up a temporary change root (chroot) to isolate the build from the rest of the filesystem. rPath encourages appliance developers to use rMake to ensure a consistent build environment.

The packaging process consists of the following sequence of events for each package or group:

  1. Creation (cvc newpkg) or clone and checkout (cvc clone and cvc co) of a package or group
  2. Developing of the package recipe or group recipe
  3. Cooking of the recipe file to check Conary messages and create a changeset that can be examined and tested (cvc cook)
  4. Troubleshooting and finalizing the recipe
  5. Committing (or checking in) the recipe to a Conary repository (cvc ci) or using rmake commit
  6. Building the package or group using Conary or rMake (cvc cook or appropriate rMake command)
  7. Troubleshooting and finalizing the build if necessary
  8. Querying the Conary repository to ensure the new build is available, and installing the build for testing


From here you may wish to:
  • Set up a build environment for recipe writing and other Conary packaging activities.
  • Reference resources to create and modify a recipe for a package or group.

Participate in the rPath Community | Contribute to rPath Wiki | Report an issue to rPath

Retrieved from "http://wiki.rpath.com/wiki/Conary:Packaging_Process"