Difference between revisions of "Add tar file to CVS and build system"
From SME Server
Jump to navigationJump to search| Line 3: | Line 3: | ||
== Adding in an updated tar file to the CVS and buildsystem == | == Adding in an updated tar file to the CVS and buildsystem == | ||
| − | # Create the new tar file on your local build system (tar -cvzf smeserver-<contrib>-<version> smeserver-<contrib>-<version>/) | + | # Create the new tar file on your local build system (tar -cvzf smeserver-<contrib>-<version>.tar.gz smeserver-<contrib>-<version>/) |
# Send it the remote buildsys (scp?) | # Send it the remote buildsys (scp?) | ||
# Login into buildsys | # Login into buildsys | ||
Revision as of 11:54, 12 July 2022
Adding in an updated tar file to the CVS and buildsystem
- Create the new tar file on your local build system (tar -cvzf smeserver-<contrib>-<version>.tar.gz smeserver-<contrib>-<version>/)
- Send it the remote buildsys (scp?)
- Login into buildsys
- cvs update -dPA in previously checked out (not anonymous) contribs10 directory (or whereever)
- Edit version number in spec file and delete patch commands
- Copy new tar file into the contribs10 directory
- "make new-sources FILES="contribs-release.tar.gz"
- cvs commit -m "comment about commit" (this simultaneously commit spec and tar file)
- logout from buildsys
- Go to contribs10 file on local build system
- prepa (or cvs update -dPA)
- Check new spec and tar file and tree (+.old) is correct!
- Mockbuild locally
- Test it.
- Build it on buildsys (make commit tag build)
