Changes

123 bytes removed ,  23:22, 24 August 2010
m
edit for readability
Line 85: Line 85:  
* Edit the spec file. Typically this involves adding a new patch, which is done by adding a <tt>PatchNN:</tt> tag and a corresponding <tt>%patchNN</tt> rule in <tt>%setup</tt>. Some of the intricacies of RPM spec files are unveiled in the [http://fedoraproject.org/wiki/Packaging/Guidelines Fedora Packaging Guidelines].
 
* Edit the spec file. Typically this involves adding a new patch, which is done by adding a <tt>PatchNN:</tt> tag and a corresponding <tt>%patchNN</tt> rule in <tt>%setup</tt>. Some of the intricacies of RPM spec files are unveiled in the [http://fedoraproject.org/wiki/Packaging/Guidelines Fedora Packaging Guidelines].
   −
* Remember to bump the revision after each change or your package won't be seen as an update relative to what is in the cache!
+
* Increase the release number after each change.
    
* <tt>make i586</tt>
 
* <tt>make i586</tt>
   −
* Wait for rpmbuild to do its job
+
* Upload rpm to a yum repository and add it to the ini file used by the OLPC OS builder.
 
  −
* Now upload this rpm to a yum repository and add it to the ini file used by the OLPC OS builder.
      
* To automate this step, we have a rule <tt>make uploadrpm</tt> which points at the Dextrose repository. Edit <tt>rpms/common/Makefile.common</tt> or <tt>rpms/common/uploadrpm</tt> to retarget this rule to your repository.
 
* To automate this step, we have a rule <tt>make uploadrpm</tt> which points at the Dextrose repository. Edit <tt>rpms/common/Makefile.common</tt> or <tt>rpms/common/uploadrpm</tt> to retarget this rule to your repository.
      
== Building custom OLPC kernels ==
 
== Building custom OLPC kernels ==
2,751

edits