Line 1: |
Line 1: |
| + | This page lists all the packages that SME Server needs to build for SME 10. The starting point is the smeos directory from SME 9. |
| + | For each package it should be checked if it is still needed, or can we use an upstream package if one is available. |
| + | |
| + | |
| + | |
| + | == Package Build Steps == |
| + | check out package |
| + | cp -a sme9 sme10 |
| + | rm -rf sme10/CVS |
| + | cd sme9 |
| + | make clean |
| + | 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} |
| + | {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 sme10 |
| + | make new-sources FILES=*xz |
| + | * will get errors here because no cvs (that's fine) |
| + | make mockbuild |
| + | * if this works then we can proceed |
| + | rpm -qpl {noarch/x86_64}/{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. |
| + | |
| + | cd .. |
| + | cvs add sme10 |
| + | cd sme10 |
| + | 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 commit tag build |
| | | |
| | | |