Building Linux Software with Conary

This paper describes best practices in Conary packaging: writing
recipes that take advantage of Conary features; avoiding redundancy with recipe inheritance and design; implementing release management using branches, shadows, labels, redirects, and flavors; and designing and writing dynamic tag handlers.  It describes how Conary policy prevents common packaging errors.  It provides examples from our rpath Linux distribution, illustrating the design principles of the Conary build process.  It then describes the steps needed to create a new distribution based on the rpath Linux distribution, using the distributed branch and shadow features of Conary.