True... But, if you think about it: how does mdk install a system?-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Stefan van der Eijk wrote:
Installing a chroot environment was quite easy.
mkdir /chroot/cooker
urpmi basesystem --root /chroot/cooker
Undocumented feature (not in man page or --help)?
I know rpm can --root.yep
What I do is I've made a user account in the chroot, and I let rpm --rebuild run from there...BTW, I have an installed 8.2 on a partition, and rpm built, but I don't know where it put the packages. If my %_topdir is on a seperate partition, do I need to mount that partition with --bind under the chroot?
copy the src.rpm to somewhere in the chroot (otherwise it can't be accessed --> I'd rather not run automount in the chroot)
cp /mirrors/${2}/SRPMS/${1}.src.rpm \
${CHROOT_PATH}/var/tmp/
run the rpm --rebuild command in the chroot:
sudo /usr/sbin/chroot ${CHROOT_PATH} \
su -l cooker \
-c "rpm --rebuild /var/tmp/${1}.src.rpm" \
&> ${buildoutput}/${2}/${HOSTTYPE}/${1}Move the resulting rpm's back to the host system:
mv ${NHOME}/RPM/RPMS/${HOSTTYPE}/* \
${HOME}/RPM/RPMS/${HOSTTYPE}/
mv ${NHOME}/RPM/RPMS/noarch/* \
${HOME}/RPM/RPMS/noarch/remove the temporary copy of the src.rpm file:
rm -rf ${CHROOT_PATH}/var/tmp/${1}.src.rpmFor more details, see the script.
Should be no problem...I've adapted slbd to run in a chroot environment. See:
http://eijk.homelinux.org/build/bin/slbd.sh
Hmm, maybe I'll take a look, but I really want to be able to build on 9.0, 8.2 and 8.1, since the only machines I have that run those releases that I am prepared to have compilers on are too slow (P133 etc, samba build takes 6+ hours).
If you need help setting it up... you know where to find me :-)
Stefan
smime.p7s
Description: S/MIME Cryptographic Signature
