Personal tools
     DOCUMENTATION

Conary:Project Directories

From rPath Wiki

Jump to: navigation, search
Conary --> Packaging --> Build Environment --> Project Directories

Conary project directories used in packaging must be on a Conary-based system and writable by all users who are using the build environment. Typically, this is a single user, and a single conary directory in the user's home directory is used to contain the build environment for that user. Though some developers choose to set up a build environment on a local system, others select a remote system to which to log in and conduct packaging activities. Both scenarios are fine provided the system has the development tools installed and sufficient access to the project repositories.

rPath recommends the following directory structure for a build environment. Note that Conary will expect to use the builds and cache directories for its internal operations:

  • ~/conary as a conary directory in your home directory on the Conary-based system)
  • ~/conary/builds where packages are actually built by Conary
  • ~/conary/cache used by Conary to store the source archives downloaded during the build process, avoiding the necessity of repetitively downloading the same source archive each time you attempt a build
  • ~/conary/src is an optional directory for storing recipe and source files, though developers may also choose to draw from a different network resource for these files
  • A subdirectory under ~/conary to represent each project, with the project name as it appears in the URL as the name of the subdirectory
  • If a developer is working with multiple branches of the same project, subdirectories under each project directory can be used to organize each branch (such as ~/conary/example/1-devel and ~/conary/example/1-test


From here you may wish to:
  • Continue setting up a build environment for Conary packaging by:
    • Installing the development tools needed for packaging in Conary
    • Ensuring you have repository access needed to commit software to one or more Conary repositories
    • Setting up the contexts, both in Conary configuration and in the directory structure, to associate local package building with upstream repositories
  • After setting up a build environment, review the Conary packaging process and start writing recipes.

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

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