5,576
edits
Changes
Jump to navigation
Jump to search
Line 163:
Line 163: + + + + + + + + + + + + + + + + + + + + + + + + + + +
Setting up RPM Building for SME Server (view source)
Revision as of 22:11, 11 February 2014
, 22:11, 11 February 2014→Testing building environment
root.log
root.log
state.log
state.log
====INSTALL AND CONFIG CVS====
If this works, it is worth grabbing either CVS for one module, or the whole CVS tree using this : http://wiki.contribs.org/Simple_Package_Modification
If this works, it is worth grabbing either CVS for one module, or the whole CVS tree using this : http://wiki.contribs.org/Simple_Package_Modification
* Setup CVS to use ssh by creating /etc/profile.d/smebuild.sh with the following content
[chris@buildcos9 profile.d]$ sudo touch smebuild.sh
[chris@buildcos9 profile.d]$ nano smebuild.sh
[chris@buildcos9 profile.d]$ sudo nano smebuild.sh
[chris@buildcos9 profile.d]$ cat smebuild.sh
# Developer environment
# This gets symlinked into /etc/profile.d
export CVS_RSH=ssh # tell CVS to use ssh
# DO NOT set CVSROOT
alias rm='rm -i'
alias cp='cp -i --preserve=timestamps'
alias mv='mv -i'
You have to logout and login again to the console for changes to take effects.
* Check CVS account
You need top create an account, then get Shad to includ you in sme group + give access to Buildsys. Can be done later...Of course it is not an issue if you have not a cvs access like we will see below, you can retrieve package in mode anonymous.
Normally you make builds from the working directory of the module you are working on, eg ~/rpms/e-smith-runit/sme9:
Normally you make builds from the working directory of the module you are working on, eg ~/rpms/e-smith-runit/sme9: