Stef:Conary Packaging Outline

From rPath Wiki

A packager should be able to...

1. Describe basic Conary concepts.
2. Query for information about installed software.
3. Query for information about software in Conary repositories.
4. Manage software on a Conary-based system.
5. Set up a Conary context for packaging for any particular Conary repository.
   1. Set up ~/.conaryrc with both a global section and context entries.
   2. Create directories and set up contexts within.
6. Check out and examine existing packages.
7. Create a new package and write the recipe.
   1. Use templates to automate new packages.
   2. Use Conary documentation and other packages' source code as references. *
8. Use cvc and rmake commands to build packages.
9. Create and install changesets to test builds before a repository commit.
10. Troubleshoot build errors in cvc and rmake. *
11. Commit builds to a Conary repository.
12. Shadow packages for label-specific customizations, and merge upstream changes. *
13. Promote to move packages between labels.

* This should be extended with distribution-specific tips, tricks, and examples.

REVIVE CONARY.COM!

We could revive conary.com as static HTML generated with DocBook XML, and we could provide both a downloadable version from conary.com as well as a Mercurial checkout of the documentation with a Creative Commons license to allow for modification (allowing those modified branches to merge changes from conary.com in the future).