Conary:cvc cook
From rPath Wiki
Conary --> Conary Commands --> cvc cook
| cvc cook | ||
| cvc cook [--prep] [--macros <file>] [--macro '<macro> <string>'] [--download] [--resume [<linenums>|policy]] [--flavor <flavor>] [--no-clean] [--unknown-flags] [--ignore-buildreqs] [--show-buildreqs] [--signature-key <fingerprint>|None] <file>[.recipe]|<component>[=<version>] | ||
| Example> cvc cook example.recipe cvc cook example | ||
Conary reads the recipe code referred to by the package name or recipe file name in its argument. Then, it attempts to apply the recipe instructions in accordance with the Conary API to build a binary entity that can be installed and managed by Conary.
In short, cvc cook is used to build packages and groups.
Unlike developer tools like rMake and rBuild, cvc cook depends solely on the Conary configuration as it applies in your current working directory.