334
edits
Changes
Jump to navigation
Jump to search
Line 85:
Line 85: − + + + − + Line 104:
Line 106: + + + Line 110:
Line 115: − − ==== Create spec file patch ==== − To create the spec file patch so new version, patch level and changelog information will be updated, issue the following command: − cvs diff e-smith-base.spec Line 135:
Line 136: +
Simple Package Modification (view source)
Revision as of 19:13, 23 January 2013
, 19:13, 23 January 2013no edit summary
==== Test the patch ====
==== Test the patch ====
To see if our changes work correctly as intended, we will make a local RPM build to test.
To see if our changes work correctly as intended, we will make a local RPM build to test, and before building the RPM it is necessary to update the spec file.
===== Update the spec file =====
First we will update the spec file (explain spec file in 1 line)
First we will update the spec file (explain spec file in 1 line)
Edit the file e-smith-base.spec and change add:
Edit the file e-smith-base.spec and change:
<pre>
<pre>
%patch55 -p1
%patch55 -p1
</pre>
</pre>
To check the changes issue the following command which compares your updated spec file with the original one in CVS. This is an optional step, but helps catch errors in the spec file.
cvs diff e-smith-base.spec
* Ensure that the changelog version really matches the RPM version.
* Ensure that the changelog version really matches the RPM version.
* Is the date really correct? Both day and date.
* Is the date really correct? Both day and date.
* The version should follow after the email address
* The version should follow after the email address
==== Update CVS ====
==== Update CVS ====
Once the patch works, attach the patch to the bugzilla entry. That is all what it takes to create a patch.
Once the patch works, attach the patch to the bugzilla entry. That is all what it takes to create a patch.
You can also, optionally, attach the updated spec file.
This simple package modification ends here. The next section is intended for developers who have CVS commit and build access. The developers will also check your patches and apply them to the CVS tree for you.
This simple package modification ends here. The next section is intended for developers who have CVS commit and build access. The developers will also check your patches and apply them to the CVS tree for you.