Chapter 4. Recipe Types and Templates

Table of Contents

4.1 -- Binary Executables
4.2 -- RPM Packages
4.3 -- Java Applications
4.4 -- C Source Code
4.5 -- Python Source Code
4.6 -- PHP Applications
4.7 -- Ruby Source Code
4.8 -- Perl Applications from CPAN
4.9 -- Custom Linux Kernel Packages
4.10 -- GNOME Applications
4.11 -- Group Recipes
4.12 -- Creating System Users and Groups with Info Packages
4.13 -- Redirect Packages and Groups

When you need to create a new package, or just determine whether existing recipe code is appropriate for your package, you can select an example recipe as a reference. Existing packages throughout rBuilder Online demonstrate a wide range of recipe approaches.

If you have a difficult time breaking down the recipe code and figuring out just what's going on, look at some of the basic recipe templates here to see how you could develop the recipe appropriate for your package.

Use these templates in conjunction with the following resources:

Completing the Build Requirements

Each template provided shows an empty buildRequires list. Conary already has a significant list of build requirements that it automatically uses, and it can report to you any other items you need to include in your own recipe. Place the empty buildRequires in your package recipe as a placeholder. Then, after you build the package for the first time, go back and add any build requirements as advised by Conary in the build messages.