Moblin/Changes File
From openSUSE
| Revision as of 21:09, 30 June 2009 Aaronbockover (Talk | contribs) � Previous diff |
Revision as of 21:10, 30 June 2009 Aaronbockover (Talk | contribs) vc script Next diff → |
||
| Line 15: | Line 15: | ||
| ==vc script== | ==vc script== | ||
| - | There is a [http://getbanshee.org/~abock/vc script called ''vc''] that inserts a new entry template to the top of a <code>.changes</code> file. Use of this script is recommended. | + | There is a [http://getbanshee.org/~abock/vc script called ''vc''] that inserts a new entry template to the top of a <code>.changes</code> file. Use of this script is recommended. Place the script in <code>$HOME/bin</code> and make it executable. |
| $ vc | $ vc | ||
Revision as of 21:10, 30 June 2009
RPM files contain a %changes section that is used to document changes that are made to the spec file/package over time.
openSUSE packages build on this by using an external package-name.changes file. During the build process, the contents of the .changes file get merged into the %changes section of the spec file.
Whenever you make a change to a package, you are expected to document your changes in the .changes file. It follows a specific format where new entries are added to the top of the file using this template:
------------------------------------------------------------------- Tue Jun 30 17:07:40 EDT 2009 - abockover@novell.com - Removed some unnecessary BuildRequires - Applied patch to fix foo, bnc#12345
The date tag is just the output of the date command line tool as run with no arguments.
vc script
There is a script called vc that inserts a new entry template to the top of a .changes file. Use of this script is recommended. Place the script in $HOME/bin and make it executable.
$ vc
Alternatively, you can specify a package/spec file name in the case where there may be multiple spec files in a package checkout:
$ vc hal
You should also create a $HOME/.vcrc file with the following line:
VC_EMAIL_ADDRESS=abockover@novell.com

