Attachment 8489 Details for Bug 19102 – How to perform a local package build

How to perform a local package build

localbuild.txt (text/plain), 1.73 KB, created by Len Lawrence on 2016-10-04 03:59:22 CEST

(hide)

Description:

Filename:

MIME Type:

Creator: Len Lawrence

Created: 2016-10-04 03:59:22 CEST

Size: 1.73 KB

patch

obsolete

>Note that this is not a packager tutorial but a note based on information provided by David Walser to help QA testers perform local builds.   
>
>First install the mgarepo and bm packages and create <before> and <after> directories.
>See /etc/mgarepo.conf.
>.....
>## uncomment it in case you don't have an account in the Mageia build system:
>#mirror = svn://svn.mageia.org/svn/packages/
>.....
>Uncomment that second line and it should use svn:// which is anonymous.
>
>Before enabling updates testing, download the sources:
>$ cd <before>
>$ mgarepo co -d 5 <packagename>
>Note the reference number which this returns in case you want to revert later on.
>To do that you would use:
>$ mgarepo co -d 5 -r <reference> <packagename>
>The -d parameter is used to indicate the Mageia version number.  Without the -d parameter everything defaults to Cauldron.
>To download the current updated sources, enable updates testing and:
>$ cd ../<after>
>$ mgarepo co -d 5 <packagename>
>These commands will create a set of source directories in <before> and <after>.
>$ ls <after>
>BUILD    BUILDROOT  RPMS     SOURCES    SPECS    SRPMS    
>
>SPECS contains <packagename>.spec, a text file containing all the build information.
>It is here that you can change the compiler, add or modify compiler flags and any flags for the link-loader (ld).  Hopefully you will not need to do that.
>
>Then to build the package:
>$ bm -ls
>Providing this is successful go on to
>$ sudo urpmi SRPMS/<packagename>*.rpm
>$ bm -l
>
>The last command provides a commentary on the build which is echoed in SPECS/log.<packagename> and will tell you if the build fails.
>
>This might be sufficient but if you also need to install the package for further tests do:
>$ sudo rpm -Uvh --force RPMS/x86_64/*.rpm
>Adjust that for i586 if needed.

Note that this is not a packager tutorial but a note based on information provided by David Walser to help QA testers perform local builds.   

First install the mgarepo and bm packages and create <before> and <after> directories.
See /etc/mgarepo.conf.
.....
## uncomment it in case you don't have an account in the Mageia build system:
#mirror = svn://svn.mageia.org/svn/packages/
.....
Uncomment that second line and it should use svn:// which is anonymous.

Before enabling updates testing, download the sources:
$ cd <before>
$ mgarepo co -d 5 <packagename>
Note the reference number which this returns in case you want to revert later on.
To do that you would use:
$ mgarepo co -d 5 -r <reference> <packagename>
The -d parameter is used to indicate the Mageia version number.  Without the -d parameter everything defaults to Cauldron.
To download the current updated sources, enable updates testing and:
$ cd ../<after>
$ mgarepo co -d 5 <packagename>
These commands will create a set of source directories in <before> and <after>.
$ ls <after>
BUILD    BUILDROOT  RPMS     SOURCES    SPECS    SRPMS    

SPECS contains <packagename>.spec, a text file containing all the build information.
It is here that you can change the compiler, add or modify compiler flags and any flags for the link-loader (ld).  Hopefully you will not need to do that.

Then to build the package:
$ bm -ls
Providing this is successful go on to
$ sudo urpmi SRPMS/<packagename>*.rpm
$ bm -l

The last command provides a commentary on the build which is echoed in SPECS/log.<packagename> and will tell you if the build fails.

This might be sufficient but if you also need to install the package for further tests do:
$ sudo rpm -Uvh --force RPMS/x86_64/*.rpm
Adjust that for i586 if needed.

Actions: View

Attachments on bug 19102: 8440 | 8444 | 8445 | 8489