Differences

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

--- developingpld:builderscript [2005-12-22 17:32] – PatrykZawadzki
+++ developingpld:builderscript [2010-05-02 13:09] (current) – SPECS -> packages grizz
@@ Line 5: / Line 5: @@
 ===== 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:
+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/SPECS
+$ 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:
@@ Line 35: / Line 37: @@
   * ''-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)
+  * ''-R'' to fetch dependant buildrequires. it is suggested that you install ''rpm-getdeps'' package for best results
 ''builder'' automatically fetches all files (including the ''spec'' file itself) 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 all file requirements are satisfied, ''builder'' launches the ''rpmbuild'' binary that initializes the build process. ''rpmbuild'' starts by checking for unsatisfied package dependencies needed to perform a successful build. If it finds any, ''builder'' will exit giving you a full list of needed packages. You can use ''poldek'' to download and install these.
 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//.
+**Warning:** all PLD packages are prepared to be built from a regular user account (without special priviledges) and you should //never use your root account// to build packages for security reasons. Keep in mind that a malfunctioning script has full write access to all your filesystems and can accidentally damage things. This is especially important when working on your own ''spec'' files as a little mistake can cost you hours or days of work.
@@ Line 46: / Line 51: @@
-<file>$ ./builder -bb -bc foo
+<file>$ ./builder -bb -bc -R foo
 </file>
 To perform a full build of a package that is currently being developed on the //DEVEL// branch: