Appliance Development:Conary Configuration

From rPath Wiki

  APPLIANCE DEVELOPMENT

Conary operations on a system are controlled by Conary configuration. Conary configuration includes such things as the default repositories Conary searches when updating software. The system-wide Conary configuration is in the file /etc/conaryrc, and users can define two scopes of configuration to supplement or override the system-wide settings:

• The current working directory: ./conaryrc
• The user's home directory: $HOME/.conaryrc

Configuration directives specified in ./conaryrc override those specified in $HOME/.conaryrc which, in turn, override those specified in the system-wide /etc/conaryrc.

A user can determine the configuration that applies to the current user and directory using conary config:

$> conary config

Because the system-wide configuration is long, users can pipe the command with less or more for a page-by-page view (such as in conary config | more), or they can grep for a specific string within the file. The following command can be used to view only the installLabelPath configuration directive, which determines the locations (labels) searched when using the conary update command:

$> conary config | grep installLabelPath
installLabelPath          foresight.rpath.org@fl:1 foresight.rpath.org@fl:1-contrib conary.rpath.com@rpl:1 
contrib.rpath.org@rpl:1 orleans.rpath.org@rpl:devel

rPath documentation provides a chart of configuration directives recognized by Conary. If desired, bookmark this page for future reference.

rPath recommends that packagers use $HOME/.conaryrc on their Conary-based systems used for appliance development. A later section shows an example $HOME/.conaryrc file and and describes how to configure contexts for packaging.