This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
developingpld:builderscript [2005-12-22 17:23] PatrykZawadzki Initial version |
developingpld:builderscript [2010-05-02 13:09] grizz SPECS -> packages |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | |||
- | |||
- | ====== The builder script ====== | ||
- | |||
- | |||
- | ===== Using the script ===== | ||
- | As the script resides in the //rpm/SPECS// subdirectory of your home, first you need to change your current directory to that of the script: | ||
- | |||
- | |||
- | |||
- | <file>$ cd | ||
- | $ cd rpm/SPECS | ||
- | </file> | ||
- | Now you can invoke ''./builder'' (remember that the dot and slash at the beginning are crucial) to see the list of possible parameters: | ||
- | |||
- | |||
- | |||
- | <file>$ ./builder | ||
- | </file> | ||
- | The general syntax is as follows: | ||
- | |||
- | |||
- | |||
- | <file>$ ./builder [options] package[.spec] | ||
- | </file> | ||
- | The ''.spec'' file extension is optional, ''builder'' will append it for you if needed. | ||
- | |||
- | Most common options are: | ||
- | |||
- | |||
- | * ''-bb'' to build only binary packages (omits creating source RPM packages) | ||
- | * ''-bc'' to cleanup after successfully building a package (removes the packaging directory as it is no longer needed) | ||
- | * ''-r BRANCH'' to use a specific branch or revision of the given package (available branches are listed at the beginning of the building process) | ||
- | * ''-U'' to fetch all the sources and update their MD5 hashes in the ''spec'' file | ||
- | * ''-5'' to update MD5 hashes using locally fetched sources | ||
- | * ''--with FEATURE'' or ''--without FEATURE'' to do a non-standard build (available features are listed at the beginning of the building process) | ||
- | ''builder'' automatically fetches all files needed to build the given package (if file license permits, otherwise you will need to manually download and save remaining files to your //~/rpm/SOURCES// directory). | ||
- | |||
- | After the build process is complete, all binary RPM files are immediately available in your //~/rpm/RPMS// directory and source RPM packages (if any) are saved to //~/rpm/SRPMS//. | ||
- | |||
- | |||
- | |||
- | ===== Examples of common use ===== | ||
- | To do a normal (binary) build of //foo// package: | ||
- | |||
- | |||
- | |||
- | <file>$ ./builder -bb -bc foo | ||
- | </file> | ||
- | To perform a full build of a package that is currently being developed on the //DEVEL// branch: | ||
- | |||
- | |||
- | |||
- | <file>$ ./builder -bc -r DEVEL foo | ||
- | </file> | ||
- | To update MD5 hashes after making changes to the above ''spec'' file: | ||
- | |||
- | |||
- | |||
- | <file>$ ./builder -r DEVEL -U foo | ||
- | </file> | ||