Changes

From SME Server
Jump to navigationJump to search
m
no edit summary
Line 85: Line 85:     
==== Test the patch ====
 
==== Test the patch ====
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.
+
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 to increase the release number and to ensure your patch is included in the build.
    
===== Update the spec file =====
 
===== Update the spec file =====
Line 104: Line 104:     
  #add patch version to the %setup section
 
  #add patch version to the %setup section
  %patch55 -p1
+
  %patch2 -p1
 
</pre>
 
</pre>
   Line 115: Line 115:  
* 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 ====
  −
CVS needs to be updated. Issue the following command:
  −
cvs update
  −
  −
* M modified, will be committed
  −
* U file has been updated since you last checked it out
  −
* A added, will be added on commit
  −
* D deleted, will be deleted on commit
  −
* ? egregious file not part of CVS record for this dir
  −
  −
* Ensure that the patch file has been added cvs add e-smith-base-5.2.0-test.patch
  −
* Ensure that your patch/files etc. are UNIX style and do not have DOS endings.
      
==== Build the test RPM ====
 
==== Build the test RPM ====
Line 143: Line 130:  
==== If you have CVS commit access ====
 
==== If you have CVS commit access ====
   −
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.):
+
==== Update CVS ====
 +
CVS needs to be updated. To check what will be committed to CVS, issue the following command:
 +
cvs update
 +
 
 +
* M modified, will be committed
 +
* U file has been updated since you last checked it out
 +
* A added, will be added on commit
 +
* D deleted, will be deleted on commit
 +
* ? egregious file not part of CVS record for this dir
 +
 
 +
* Ensure that the patch file has been added cvs add e-smith-base-5.2.0-test.patch
 +
* Ensure that your patch/files etc. are UNIX style and do not have DOS endings.
 +
 
 +
Once you are satisfied and want to submit the package to CVS 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.):
 
  cvs commit -m 'your descriptive commit message here'
 
  cvs commit -m 'your descriptive commit message here'
  

Navigation menu