Freeside:Documentation:CreatingRPMRepo - Revision history

Ivan: Freeside:1.7:Documentation:CreatingRPMRepo moved to Freeside:Documentation:CreatingRPMRepo

2009-07-26T20:50:24Z

Freeside:1.7:Documentation:CreatingRPMRepo moved to Freeside:Documentation:CreatingRPMRepo

Rsiddall: /* Set up your development environment for building RPMs as non-root */

2008-10-27T18:31:55Z

‎Set up your development environment for building RPMs as non-root

Rsiddall: /* Building Modified RPMs */

2008-02-13T01:19:02Z

‎Building Modified RPMs

Rsiddall: /* Create the Freeside RPMs */ Removing obsolete notes about having to build from the directory containing the specfile.

2008-02-13T01:18:29Z

‎Create the Freeside RPMs: Removing obsolete notes about having to build from the directory containing the specfile.

Rsiddall: /* Set up your development environment for building RPMs as non-root */

2008-02-13T01:15:32Z

‎Set up your development environment for building RPMs as non-root

Rsiddall: Removed section on freeside-mason-deps.inc as that file has been obsoleted by latest changes to the .spec file.

2007-12-14T19:44:55Z

Removed section on freeside-mason-deps.inc as that file has been obsoleted by latest changes to the .spec file.

Ivan at 23:20, 26 November 2007

2007-11-26T23:20:14Z

Ivan: /* Create the repository */

2007-11-21T00:28:24Z

‎Create the repository

Ivan: /* Create the repository */

2007-11-21T00:22:11Z

‎Create the repository

Ivan at 17:03, 20 November 2007

2007-11-20T17:03:07Z

@@ Line 22: / Line 22: @@
 <pre>
 su bob
 mkdir ~/redhat/{BUILD,RPMS,SOURCES,SPECS,SRPMS}
 </pre>

@@ Line 37: / Line 37: @@
 You can also get tarballs from CVS using ViewVC.
 ===Building Modified RPMs===
-* Instead of using the tarbuild, untar the tarball:
+Instead of using the tarbuild, untar the tarball:
 <pre>
 mkdir ~/work
@@ Line 43: / Line 43: @@
 tar zxvf ~/redhat/SOURCES/freeside-1.7.3.tar.gz
 </pre>
-* If you are building modified RPMs, copy your patches and supplemental files to ~/redhat/SOURCES and edit the specfile to make use of them.
+Copy your patches and supplemental files to ~/redhat/SOURCES and edit the specfile to make use of them.
-* Next, build the RPMs:
+Next, build the RPMs:
 <pre>
 rpmbuild -ba freeside.spec

@@ Line 31: / Line 31: @@
 wget http://www.sisd.com/freeside/freeside-1.7.3.tar.gz
 </pre>
-(Ideally you could build the RPMs at this point using a tarbuild: rpmbuild -ta freeside.tar.gz. This doesn't work yet.)
+Next, build the RPMs using a tarbuild:
 You can also get tarballs from CVS using ViewVC.
-* Next, untar the tarball and change directory to the folder containing the RPM specfile:
+===Building Modified RPMs===
 <pre>
 mkdir ~/work
 cd ~/work
 tar zxvf ~/redhat/SOURCES/freeside-1.7.3.tar.gz
 </pre>
 * If you are building modified RPMs, copy your patches and supplemental files to ~/redhat/SOURCES and edit the specfile to make use of them.
@@ Line 45: / Line 48: @@
 rpmbuild -ba freeside.spec
 </pre>
 =Build the RPMs for required Perl modules=
 Freeside uses many Perl modules, not all of which are available as RPMs. The simplest way of generating all the required RPMs is to use Ovid, which is available from CPAN, as Ovid works recursively to build RPMs of modules that the current module depends on.  Ovid also can build RPM sets from Perl bundle files.

@@ Line 24: / Line 24: @@
 mkdir ~/redhat/{BUILD,RPMS,SOURCES,SPECS,SRPMS}
 </pre>
-To build Freeside RPMs as a non-root user, your build system must have a freeside user:
 =Create the Freeside RPMs=
 * First, get the Freeside source code as a tarball

@@ Line 48: / Line 48: @@
 rpmbuild -ba freeside.spec
 </pre>
 =Build the RPMs for required Perl modules=
 Freeside uses many Perl modules, not all of which are available as RPMs. The simplest way of generating all the required RPMs is to use Ovid, which is available from CPAN, as Ovid works recursively to build RPMs of modules that the current module depends on.  Ovid also can build RPM sets from Perl bundle files.

← Older revision	Revision as of 20:50, 26 July 2009
(No difference)

← Older revision		Revision as of 23:20, 26 November 2007
Line 209:		Line 209:
	</pre>		</pre>
	Once this file is installed in /etc/yum.repos.d, you can proceed to [[Freeside:1.7:Documentation:InstallingUsingRPM\|install Freeside from the repository]].		Once this file is installed in /etc/yum.repos.d, you can proceed to [[Freeside:1.7:Documentation:InstallingUsingRPM\|install Freeside from the repository]].
		+
		+	= The short version =
		+
		+	== One-time setup ==
		+
		+	* Create a build environment matching your target.
		+	* Set up your development environment for building RPMs as non-root.
		+	* If you think you're going to add Perl dependencies, install one of Ovid (modified as in the wiki), cpan2rpm (see the installation instructions for CentOS 4.4 for details on installing this), or RPM::Specfile (for cpanflute2). Not necessary if you're just doing minor bug fixes.
		+	* If you think you're going to distribute the revised Freeside RPMs via a repository, install createrepo using yum.
		+	* Checkout the 1.7 branch from CVS into the build user's working area.
		+
		+	== Updates ==
		+
		+	=== Build the new RPMs ===
		+
		+	* Do a CVS update on the working copy.
		+	* Create a new tarball and copy it to the SOURCES directory.
		+	* cd to the working copy's install/rpm directory.
		+	* run rpmbuild --define='release RELEASE' -ba freeside.spec
		+
		+	Example script to build from a local CVS working tree:
		+
		+	<pre><nowiki>
		+	#!/bin/sh
		+	VERSION=1.7
		+	RELEASE=`date +%Y%m%d`
		+	cd freeside-${VERSION}
		+	cvs update
		+	cd ..
		+	tar zcvf /home/rsiddall/redhat/SOURCES/freeside-${VERSION}.tar.gz \
		+	--exclude CVS freeside-${VERSION}
		+	cd freeside-${VERSION}/install/rpm
		+	rpmbuild --define="version $VERSION" --define="release $RELEASE" -ba \
		+	freeside.spec
		+	</nowiki></pre>
		+
		+	Your RPMs should build successfully. About 6 to 12 lines before the end of
		+	the build output you should see a bunch of lines like:
		+	Wrote: /home/bob/redhat/SRPMS/freeside-1.7-20071113.src.rpm
		+	Wrote: /home/bob/redhat/RPMS/noarch/freeside-1.7-20071113.noarch.rpm
		+	which tells you the RPMs were created.
		+
		+	=== Additional checks ===
		+
		+	You can do some optional checking at this point with "rpm -q", for
		+	example:
		+	rpm -qlp /path/to/RPM # List of all the files packaged in the RPM
		+	rpm -qp --requires /path/to/RPM # List of dependencies
		+	rpm -qip /path/to/RPM # Cataloging data.
		+	rpm -qp --scripts /path/to/RPM # Dump all the RPM-related scripts.
		+	This is mainly useful for checking against the previous RPM to see
		+	nothing unexpected changed.
		+
		+	=== Sign the RPMs ===
		+
		+	rpm --addsign <list of rpms>
		+
		+	=== Upload to repository ===
		+
		+	Put them in a folder in web server space and run
		+	createrepo <folder> to update the yum metadata for the repo. (Also yum-arch if the target system is RHEL rather then CentOS)
		+
		+	=== Update target system ===
		+
		+	Update the target system with up2date or yum.

@@ Line 190: / Line 190: @@
 <pre>cd /var/www/html/fedora/7
 rpm --addsign *.rpm</pre>
-* Download any programs needed to build the repository.  For newer, XML-based versions of yum, you'll need createrepo. If it's in a yum repository, this can be as simple as:<pre>yum install createrepo</pre>. On distros using older versions of yum (e.g. FC2 and earlier), you'll need to use yum-arch instead of createrepo to generate the repository metadata. yum-arch should be installed as part of the yum RPM, so there's no need to install another RPM.
+* Download any programs needed to build the repository.  For newer, XML-based versions of yum, you'll need createrepo. If it's in a yum repository, this can be as simple as:<pre>yum install createrepo</pre>. On distros using older versions of yum (e.g. FC2 and earlier), you'll need to use yum-arch instead of createrepo to generate the repository metadata. yum-arch should be installed as part of the yum RPM, so there's no need to install another RPM.  You should also use yum-arch when creating a new-style repository if you intend for it to be accessed from official RHEL v4 using up2date.
 * Create the repository:
 <pre>createrepo /var/www/html/fedora/7
 </pre>
 * Make sure the web server is started

@@ Line 207: / Line 207: @@
 gpgkey=http://localhost/RPM-GPG-KEY-yourname
 </pre>
-Once this file is installed in /etc/yum.repos.d, you can proceed to [[#yum|install Freeside from the repository]].
+Once this file is installed in /etc/yum.repos.d, you can proceed to [[Freeside:1.7:Documentation:InstallingUsingRPM|install Freeside from the repository]].

@@ Line 180: / Line 180: @@
 *** Next, create the HTML::Mason specfile and hand-edit it to insert all these dependencies.  (There is no perl-Bundle-HTML-Mason RPM, so you have to list all the dependencies individually.)
 *** Finally, rebuild the HTML::Mason RPM using rpmbuild.  Be aware that Ovid will overwrite your customized specfile if it thinks it needs to build HTML::Mason again.
-==Create the repository==
+=Create the repository=
 * Copy all generated RPMs into your web server space:
 <pre>