2,569
edits
Changes
Jump to navigation
Jump to search
Line 185:
Line 185: − Then tag all files as belonging to a particular build version+ + + + − Then submit the request to the build server which will checkout the recently tagged version and build it in a chroot (mock) env.+ − Key things are to always do "make tag" before "make build" + − + − CVS cheat sheet [[:Package_Modification/More cvs commands]]+ − − − =====buildsys follow up ===== − − − You are notified by email of success or failure of your build request
Package Modification (view source)
Revision as of 09:49, 17 September 2008
, 09:49, 17 September 2008→Modify a package
cvs commit -m "$(make clog)"
cvs commit -m "$(make clog)"
CVS cheat sheet [[:Package_Modification/More cvs commands]]
=====Build=====
Tag all files as belonging to a particular build version
make tag
make tag
Submit the request to the build server which will checkout the recently tagged version and build it
make build
make build
Always do "make tag" before "make build"
Always ensure you are working with the latest version (cvs update -dPA)
Always ensure you are working with the latest version (cvs update -dPA)
You and updatesteam will get an email on successfull build.
You and updatesteam will get an email on successful build.
Only you will get an email on failed build.
Only you will get an email on failed build.
You can check the build system is working:
You can check the buidsys working thanks to plague:
* [https://buildsys.contribs.org/plague https://buildsys.contribs.org/plague]
* [https://buildsys.contribs.org/plague https://buildsys.contribs.org/plague]
* or in shell
* or in shell
plague-client list uid {task number}
plague-client list uid {task number}
====Releasing a package====
====Releasing a package====