2,569
edits
Changes
Jump to navigation
Jump to search
Line 78:
Line 78: − # cd to work directory+ − + − # + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
→Go to work
make patch SUFFIX=<stuff>
make patch SUFFIX=<stuff>
change to work directory
cd smecontribs/rpms/smeserver-foo/contribs7
cd smecontribs/rpms/smeserver-foo/contribs7
For more information
make help
To prepare a tree
cvs update -dPA
make clean
make prep
You can switch to the tree and make modification.
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.
Binary files are stored in a look-aside cache on shads box. CVS isn't great on binary files.
In the prepared dir copy a file you want to modify like so:
cp 28UserManagerProxyPass 28UserManagerProxyPass.{patchname}
Then modify the original file 28UserManagerProxyPass
To add new files touch the file.{patchname} so it is empty. [Check]
Once you have all the files you want patched copied and changed then you can build the patch (from the contribs7 dir) with:
make patch SUFFIX={patchname}
It will build and add the patch for you. It should be named "name-version-{patchname}.patch"
Read up on gendiff. That is what the makefile uses to generate the diff file.
Once you are satisfied and want to submit the package to the build server you can do the following.
This tags all files as belonging to a particular build version
make tag
This will submit the request to the build server which will checkout the recently tagged version and build it in a chroot (mock) env.
make build
Once the commit is done you can test a build locally [check, can we make local before a commit]
make local
Key things are to always do "make tag" before "make build"
always ensure you are working with the latest version (cvs update -dPA)
issue from rpms, or a directory below
You and updatesteam will get an email on successfull build.
Only you will get an email on failed build.
===Workflow===
===Workflow===