From e4168be65eaff79d157f3e6a2073410c6ce5fe9b Mon Sep 17 00:00:00 2001 From: Thierry Parmentelat Date: Thu, 22 Nov 2007 13:32:34 +0000 Subject: [PATCH] another readme --- README-build.txt | 39 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 39 insertions(+) create mode 100644 README-build.txt diff --git a/README-build.txt b/README-build.txt new file mode 100644 index 00000000..0f1271de --- /dev/null +++ b/README-build.txt @@ -0,0 +1,39 @@ +Notes on using this build + +* install a vserver-enabled kernel and util-vserver on your build box +* create a local fedora mirror - see vbuild-fedora-mirror.sh +* create a vserver - see vbuild-init-vserver.sh +* enter the vserver and svn export this build module into /build +* cd /build and ru +# make stage1=true PLDISTRO=yourdistro +# make help +# make + +=== automated builds +* the nightly build script wraps all this in a rather complicated way +it is not intended to be used as is without a few manual tweaks on your +build and test hosts +basically it +** recreates a fresh build vserver named after the arguments +** enters this to perform the actual build +** pushes the results to a web location so the tests can pull the +right myplc rpm +** invokes a runtest on a separate machine +** manages logs - that's the trickiest part, so the root context and +the vserver add their logs on the same file + +=== manual builds +* always run the stage1 make prior to anything else +* if you clean or patch a spec file you need to run the stage1 again +* see make help for how to do things incrementally + +* typically if you want to test a change without commiting first, you +need to: +** make package-codebase +** patch CODEBASE/module/ +** make package + +if further changes are needed, then do +** make package-clean-tarball package-clean-build package-clean-rpm +so the codebase remains intact, patch it again and run +** make package -- 2.47.0