2,569
edits
Changes
Jump to navigation
Jump to search
Line 86:
Line 86: − + Line 108:
Line 108: − + − + − You can switch to the tree and make modification.+ Line 118:
Line 118: − + Line 128:
Line 128: + + + − + Line 138:
Line 141: − − Once the commit is done you can test a build locally [check, can we make local before a commit] − make local − + − Issue from rpms directory, or a directory below, anywhere with a CVS directory
→Modify a package
====Modify a package====
====Modify a package====
Builders have rights to patch packages, tag, and build.
Builders have rights to patch packages, tag, and build.
If you need to upload new source tarballs or versions shad has to do that for now.
If you need to upload new source tarballs or versions shad has to do that for now. Email them.
Binary files are stored in a look-aside cache on shads box. CVS isn't great on binary files.
Binary files are stored in a look-aside cache on shads box. CVS isn't great on binary files.
To prepare a tree
To prepare a tree
cvs update -dPA
cvs update -dPA [optional]
make clean
make clean [optional]
make prep
make prep
Then switch to the tree and make modification.
In the prepared dir copy a file you want to modify like so:
In the prepared dir copy a file you want to modify like so:
cp 28UserManagerProxyPass 28UserManagerProxyPass.{patchname}
cp 28UserManagerProxyPass 28UserManagerProxyPass.{patchname}
Then modify the original file 28UserManagerProxyPass
Then modify the original file 28UserManagerProxyPass.
To add new files touch the file.{patchname} so it is empty.
To add new files touch the file.{patchname} so it is empty.
Edit the spec
Edit the spec
nano -w smeserver-foo.spec
nano -w smeserver-foo.spec
Build the rpm locally to test
make local
Once you are satisfied and want to submit the package to the build server commit your changes.
Once you are satisfied and want to submit the package to the build server commit your changes.
cvs commit
cvs commit
:q [quit out of log message] ??
:q enter [is this right ?? messy]
Then tag all files as belonging to a particular build version
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.
Then submit the request to the build server which will checkout the recently tagged version and build it in a chroot (mock) env.
make build
make build
Key things are to always do "make tag" before "make build"
Key things are to 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 successfull build.