334
edits
Changes
From SME Server
Jump to navigationJump to searchSetting up RPM Building for SME Server (view source)
Revision as of 18:16, 27 January 2013
, 18:16, 27 January 2013→Testing building environment
You can then run a test by doing:
You can then run a test by doing:
# e.g. initialise a centos-5-i386 chroot environment
# e.g. initialise a smeserver-8-x86_64-base chroot environment
$ CONFIG=centos-5-i386
$ CONFIG=smeserver-8-x86_64-base
$ mock -r $CONFIG --init
$ mock -r $CONFIG --init
which will setup an initial chroot environment using the given config. If that seemed to work (you weren't inundated with error messages), you can try a build:
which will setup an initial chroot environment using the given config. If that seemed to work (you weren't inundated with error messages), you can try a build:
Notes:
Notes:
* Using the provided .cfg files I have verified smeserver-8-x86_64-base.cfg & smeserver-9-x86_64-base.cfg and managed to build e-smith-runit for SME 9
* the chroot environments are cached, but rebuilding them and checking for updates can be pretty network intensive, so you might want to consider setting up a local repository to pull from. mrepo (available from rpmforge) is pretty good for that.
* the chroot environments are cached, but rebuilding them and checking for updates can be pretty network intensive, so you might want to consider setting up a local repository to pull from. mrepo (available from rpmforge) is pretty good for that.
*there don't seem to be any hooks in mock to allow you to sign packages you've built, so if you do want signed packages you need to sign them afterwards via a rpm --resign $RPMS.
*there don't seem to be any hooks in mock to allow you to sign packages you've built, so if you do want signed packages you need to sign them afterwards via a rpm --resign $RPMS.
