View source for RPM - Preparing the Package Building Environment

<div class="navheader"><table summary="Navigation header" width="100%"><tr><th align="center" colspan="3">Chapter&nbsp;2.&nbsp;Preparing the Package Building Environment</th></tr><tr><td align="left" width="20%">[[RPM - Introduction|Prev]]&nbsp;</td><th align="center" width="60%">&nbsp;</th><td align="right" width="20%">&nbsp;[[RPM - Using the Adempiere SRPM|Next]]</td></tr></table><hr></div>


<div>
=<span id="N104E6">Preparing the Package Building Environment</span>=
</div><div><div class="titlepage"><div><div>
==<span id="N104EA">Required Development Tools</span>==
</div></div></div><p>
				Install the tools required for building the <span class="productname">Adempiere</span> RPM. (This needs to be done as <code class="code">root</code>).
			</p><div class="informalexample"><p>
					<code class="prompt"># </code><span class="command"><strong>yum install rpm-build rpmdevtools gnupg mercurial java-1.6.0-openjdk-devel desktop-file-utils docbook5-style-xsl libxslt fop</strong></span>
				</p></div></div><div><div class="titlepage"><div><div>
==<span id="N104FE">RPM Build Tree</span>==
</div></div></div><p>
				Create the RPM build tree in your home directory.
			</p><div class="informalexample"><p>
					<code class="prompt">$ </code><span class="command"><strong>rpmdev-setuptree</strong></span>
				</p></div><p>
				This command creates the following directory tree required by <span class="command"><strong>rpmbuild</strong></span> and configures your build settings
				in <code class="filename">~/.rpmmacros</code>
			</p><pre id="N10514">
rpmbuild
+-- BUILD
+-- RPMS
+-- SOURCES
+-- SPECS
+-- SRPMS
			</pre><p>
				You can move the generated <code class="filename">rpmbuild</code> directory to any place you like, but then you must adjust
				the <code class="varname">%_topdir</code> setting in <code class="filename">~/.rpmmacros</code> to point to that location.
			</p></div><div><div class="titlepage"><div><div>
==<span id="secGpgSign">Digital Signature</span>==
</div></div></div><p>
				For security reasons, the packages you build should be digitally signed. The digital signature allows users to verify
				that the package has been built by you, a trusted source, and has not been tampered with since then.
			</p><p>
				First, generate a public/private key pair with the <span class="command"><strong>gpg --gen-key</strong></span> command:
			</p><pre id="N1052D">
$ gpg --gen-key
gpg (GnuPG) 1.4.10; Copyright (C) 2008 Free Software Foundation, Inc.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Please select what kind of key you want:
	(1) RSA and RSA (default)
	(2) DSA and Elgamal
	(3) DSA (sign only)
	(4) RSA (sign only)
Your selection? 1
RSA keys may be between 1024 and 4096 bits long.
What keysize do you want? (2048) 2048
Requested keysize is 2048 bits
Please specify how long the key should be valid.
				0 = key does not expire
			&lt;n&gt;  = key expires in n days
			&lt;n&gt;w = key expires in n weeks
			&lt;n&gt;m = key expires in n months
			&lt;n&gt;y = key expires in n years
Key is valid for? (0) 0
Key does not expire at all
Is this correct? (y/N) y

You need a user ID to identify your key; the software constructs the user
ID from the Real Name, Comment and Email Address in this form:
		"Heinrich Heine (Der Dichter) &lt;heinrichh@duesseldorf.de&gt;"

Real name: www.mycompany.com
Email address: devnull@mycompany.com
Comment: rpm signature

You selected this USER-ID:
		"www.mycompany.com (rpm signature) &lt;devnull@mycompany.com&gt;"

Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? O
You need a Passphrase to protect your secret key.

Enter passphrase: secret passphrase
Repeat passphrase: secret passphrase

We need to generate a lot of random bytes. It is a good idea to perform
some other action (type on the keyboard, move the mouse, utilize the
disks) during the prime generation; this gives the random number
generator a better chance to gain enough entropy.
.+++++
........+++++
..+++++
gpg: key F9D8EE90 marked as ultimately trusted
public and secret key created and signed.

gpg: checking the trustdb
gpg: 3 marginal(s) needed, 1 complete(s) needed, classic trust model
gpg: depth: 0  valid:   2  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 2u
pub   2048R/F9D8EE90 2010-10-17
			Key fingerprint = 983D 704A 024A 861F 9FCB  5CA2 4875 7B66 F9D8 EE90
uid   www.mycompany.com (rpm signature) &lt;devnull@mycompany.com&gt;
sub   2048R/496CD9ED 2010-10-17
			</pre><p>
				Next, the public key needs to be extracted:
			</p><div class="informalexample"><p>
					<code class="prompt">$ </code><span class="command"><strong>gpg --export --armor www.mycompany.com &gt; MYCOMPANY-RPM-GPG-KEY</strong></span>
				</p></div><p>
				This file needs to be publicly distributed so that users can verify the signature of the RPM packages which you built and signed.
			</p><p>
				Finally, you need to configure <span class="command"><strong>rpmbuild</strong></span> to use the signature you just created
				by adding the <code class="varname">%_signature</code> and <code class="varname">%_gpg_name</code> macros to the <code class="filename">.rpmmacros</code>
				file in your home directory. The file should now look something like this:
			</p><pre id="N1056D">
%_topdir        /home/username/rpmbuild
%_signature     gpg
%_gpg_name      www.mycompany.com (rpm signature) &lt;devnull@mycompany.com&gt;
&hellip;
&hellip;
			</pre></div>
<div class="navfooter"><hr><table summary="Navigation footer" width="100%"><tr><td align="left" width="40%">[[RPM - Introduction|Prev]]&nbsp;</td><td align="center" width="20%">&nbsp;</td><td align="right" width="40%">&nbsp;[[RPM - Using the Adempiere SRPM|Next]]</td></tr><tr><td valign="top" align="left" width="40%">Chapter&nbsp;1.&nbsp;Introduction&nbsp;</td><td align="center" width="20%">[[RPM|Home]]</td><td valign="top" align="right" width="40%">&nbsp;Chapter&nbsp;3.&nbsp;Using the Adempiere SRPM</td></tr></table></div>