Personal tools
     DOCUMENTATION

Conary:Repository Access for Packaging

From rPath Wiki

Jump to: navigation, search
Conary --> Packaging --> Build Environment --> Repository Access

Developers can work on collaborative projects and individual projects. In both cases, the developer requires network access and write permissions for the project repository associated with each project. The developer can use the ping utility or other means to test access from the Conary-based system to the repository. In the case of rBuilder (including rBuilder Online), write access to a project repository is granted if the developer's rBuilder user has developer or project owner permissions on the rBuilder project. Ask project owners or repository administrators to provide credentials when necessary.

Root access to the local system is not necessary. Conary does not allow developers to build as root in the build environment. Also, changesets created by cooking recipes can be moved to test systems to bypass testing on the same system as the build environment.


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
    • Creating project directories to contain the Conary contexts where packaging occurs
    • 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:Repository_Access_for_Packaging"