Changes

From SME Server
Jump to navigationJump to search
merging info on same topic
Line 131: Line 131:  
==== Results ====
 
==== Results ====
 
Please add your notes to this page: [[SME9BuildQueue]]
 
Please add your notes to this page: [[SME9BuildQueue]]
 +
 +
 +
 +
METHOD 2 (needs merging)
 +
== Package Build Steps ==
 +
check out package
 +
cp -a sme8 sme9
 +
rm -rf sme9/CVS
 +
cd sme9
 +
make prep
 +
 +
mv {sourcedir} {newsourcedir}
 +
* example e-smith-base-5.2.0 to e-smith-base-5.4.0
 +
rm -f *.patch
 +
* apply any fixes from spec to tree, only for SME Server packages
 +
* move lib/perl5/site_perl to share/perl5/vendor_perl
 +
tar Jcvf {newsource}.tar.xz {newsourcedir}
 +
 +
vi *.spec
 +
* remove patches and fixes applied directly to tree
 +
* bump version and reset release to 1
 +
* add changelog saying rolling for sme9
 +
make mockbuild
 +
* if this works then we can proceed
 +
rpm -qpl {package-version}_sme/{rpmname}.rpm
 +
* check that files look similar to the sme8 package
 +
 +
 +
=== These following steps need developer access ===
 +
They are here for reference, and transparency. They will need to be run on SME Server's build server.
 +
You do not need to do this part.  (If you have CVS access but not access to the build servers please don't run any of these commands)
 +
 +
cd ..
 +
cvs add sme9
 +
cd sme9
 +
 +
date +%s
 +
* get date for import
 +
vi import.log*
 +
* fix name/version/release and date
 +
cvs add .cvsignore *.spec Makefile import.log sources
 +
* be sure to add any other needed packages
 +
make new-sources FILES=*xz
 +
 +
make commit tag build
 +
 +
== Package List from SME Server 8, smeos ==
 +
 +
* For each of these packages a volunteer can add their name, and carry out the Package Build Steps above.
 +
* Check if the package is already built for SME 9 or has a sme9 directory in CVS before starting
 +
* When something does not build, create a bug.
 +
* To set up mock as used above see [[Setting_up_RPM_Building_for_SME_Server|Building using Mock]]
 +
* To checkout packages from CVS see [[Simple_Package_Modification|Simplest way to develop patches to submit]]
 +
 +
* If you have problems on setting up the environment, ask on IRC or Devinfo.
 +
     

Navigation menu