PLD Linux Distribution

User Tools

Site Tools

Trace:
developingpld:builderscript

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
developingpld:builderscript [2006-09-12 20:36] – recovered entry rootdevelopingpld:builderscript [2010-05-02 13:09] (current) – SPECS -> packages grizz
Line 2: Line 2:
  
 ====== The builder script ====== ====== The builder script ======
-Before you can use ''builder'' script, You should have  [[:DevelopingPLD:PreparingWorkingEnvironment|working build environment]] setup.  
- 
  
  
 ===== Using the script ===== ===== Using the script =====
-You can invoke ''builder'' (note that as the script is now in ''rpm-build-tools'', you no longer need to change the working directory) to see the list of possible parameters: +Before you start be sure your [[:DevelopingPLD:PreparingWorkingEnvironment|working enviroment]] is setup.  
 + 
 +As the script resides in the //rpm/packages// subdirectory of your home, first you need to change your current directory to that of the script:  
 + 
 + 
 + 
 +<file>$ cd 
 +$ cd rpm/packages 
 +</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>$ ./builder
 </file> </file>
 The general syntax is as follows:  The general syntax is as follows: 
Line 17: Line 24:
  
  
-<file>$ builder [options] package[.spec]+<file>$ ./builder [options] package[.spec]
 </file> </file>
 The ''.spec'' file extension is optional, ''builder'' will append it for you if needed.  The ''.spec'' file extension is optional, ''builder'' will append it for you if needed. 
Line 26: Line 33:
   * ''-bb'' to build only binary packages (omits creating source RPM packages)    * ''-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)    * ''-bc'' to cleanup after successfully building a package (removes the packaging directory as it is no longer needed) 
-  * ''--date DATE'' to build a specific release from the past (to make sure you also get proper SOURCES)  
   * ''-r BRANCH'' to use a specific branch or revision of the given package (available branches are listed at the beginning of the building process)    * ''-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    * ''-U'' to fetch all the sources and update their MD5 hashes in the ''spec'' file 
Line 45: Line 51:
  
  
-<file>$ builder -bb -bc -R foo+<file>$ ./builder -bb -bc -R foo
 </file> </file>
 To perform a full build of a package that is currently being developed on the //DEVEL// branch:  To perform a full build of a package that is currently being developed on the //DEVEL// branch: 
Line 51: Line 57:
  
  
-<file>$ builder -bc -r DEVEL foo+<file>$ ./builder -bc -r DEVEL foo
 </file> </file>
 To update MD5 hashes after making changes to the above ''spec'' file:  To update MD5 hashes after making changes to the above ''spec'' file: 
Line 57: Line 63:
  
  
-<file>$ builder -r DEVEL -U foo+<file>$ ./builder -r DEVEL -U foo
 </file> </file>
  
developingpld/builderscript.1158086181.txt.gz · Last modified: 2006-09-12 20:36 by root
Except where otherwise noted, content on this wiki is licensed under the following license: Public Domain
Public Domain Donate Powered by PHP Valid HTML5 Valid CSS PLD Linux Driven by DokuWiki