Changes

Jump to navigation Jump to search
no edit summary
Line 77: Line 77:  
  </pre>
 
  </pre>
   −
[Reformatted upto here]
+
* CHECK: that the changelog version really matches the RPM version.
 
+
* CHECK: Is the spec file correct, look at the changes
CHECK: that the changelog version really matches the RPM version.
  −
 
  −
CHECK: Is the spec file correct, look at the changes
      +
==== Applying the patch ====
 
cvs diff e-smith-base.spec
 
cvs diff e-smith-base.spec
 
   Have you updated the release? Is that new release in the changelog?
 
   Have you updated the release? Is that new release in the changelog?
Line 97: Line 95:  
CHECK: what would be committed
 
CHECK: what would be committed
    +
==== Update CVS ====
 
cvs update
 
cvs update
 
     * M modified, will be committed
 
     * M modified, will be committed
Line 108: Line 107:  
CHECK: are the files UNIX or do they have DOS endings (bad)
 
CHECK: are the files UNIX or do they have DOS endings (bad)
    +
==== Build a test RPM ====
 
Build the rpm locally to test, (note, this deletes the working tree!)  
 
Build the rpm locally to test, (note, this deletes the working tree!)  
 +
make local
   −
make local
+
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.
      +
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 ---
     −
***If you have CVS access then
+
== Committing the patch ==
 +
==== If you have CVS access then ====
    
Once you are satisfied and want to submit the package to the build server commit your changes. (Please use descriptive comments so that other developers are aware of what is happening. Comments will appear on the subject line of the commit email that get send to the other developers.)  
 
Once you are satisfied and want to submit the package to the build server commit your changes. (Please use descriptive comments so that other developers are aware of what is happening. Comments will appear on the subject line of the commit email that get send to the other developers.)  
Line 124: Line 123:  
cvs commit -m ''  <-- copy this then add changelog line
 
cvs commit -m ''  <-- copy this then add changelog line
   −
***If you have build access then
+
==== If you have build access then ====
 
   
Build it (from either the sme7 or sme8 dir):
 
Build it (from either the sme7 or sme8 dir):
 
+
make tag
make tag
+
make build
make build
 

Navigation menu