Line 3: |
Line 3: |
| This article is only about setting up your smeserve build server. To use it, you should follow one of the other articles (e.g. [[Simple Package Modification]]) | | This article is only about setting up your smeserve build server. To use it, you should follow one of the other articles (e.g. [[Simple Package Modification]]) |
| | | |
| + | ==== The Server ==== |
| This is what I did after reading a number of older wiki articles re: developing and amending packages as well as development environment setup. | | This is what I did after reading a number of older wiki articles re: developing and amending packages as well as development environment setup. |
| | | |
Line 24: |
Line 25: |
| * add a developer user | | * add a developer user |
| | | |
− | Now we ssh into our server as root, to finish setting up our developer user:<syntaxhighlight lang="bash"> | + | Now we ssh into our server as root, to finish setting up our developer user: |
| + | <syntaxhighlight lang="bash"> |
| db accounts setprop <userid> Shell /bin/bash | | db accounts setprop <userid> Shell /bin/bash |
| chsh -s /bin/bash <userid> | | chsh -s /bin/bash <userid> |
Line 32: |
Line 34: |
| yum --enablerepo=smedev,epel,extras install plague-client mock python-ctypes glances e-smith-devtools smeserver-mock | | yum --enablerepo=smedev,epel,extras install plague-client mock python-ctypes glances e-smith-devtools smeserver-mock |
| signal-event post-upgrade; signal-event reboot | | signal-event post-upgrade; signal-event reboot |
− | </syntaxhighlight>Now you need to login as your developer and set them up: | + | </syntaxhighlight> |
| + | Now you need to login as your developer and set them up: |
| | | |
− | You will need to tweak their shell for CVS access and whilst there, why not make it a little friendlier :)<syntaxhighlight lang="bash"> | + | You will need to tweak their shell for CVS access and whilst there, why not make it a little friendlier :) |
| + | <syntaxhighlight lang="bash"> |
| cat <<_EOT > ~/.bashrc | | cat <<_EOT > ~/.bashrc |
| # .bashrc | | # .bashrc |
Line 73: |
Line 77: |
| </syntaxhighlight> | | </syntaxhighlight> |
| | | |
− | ==== CVS shell.koozali.org access ==== | + | ==== Developer access==== |
− | | + | You don't need to have developer access to copy out source, local compiles, etc., but you do need it if you are going to want to save changes back into cvs or git. |
− | * SME Server code is stored in the CVS on [[/shell.koozali.org/|http://shell.koozali.org]]. To be able to work on your code in the SME Server CVS repository you need an account on Koozali.org. With this account the development team can give you access to the CVS repository. | + | *SME Server code is stored in the CVS on [[/shell.koozali.org/|http://shell.koozali.org]] and in the future in git on https://src.koozali.org. To be able to work on your code in the SME Server CVS repository you need an account on Koozali.org. With this account the development team can give you access to the CVS repository. |
| | | |
| * After your Koozali.org account has been created you can ask the development team to give you developer access to smecontribs. Create a bug in the Bug Tracker as usual. | | * After your Koozali.org account has been created you can ask the development team to give you developer access to smecontribs. Create a bug in the Bug Tracker as usual. |
− | * You will be sent your shell keys (store in ~/.ssh/) and plague keys (store in ~/.buildsys/) | + | *You will be sent your shell keys (store in ~/.ssh/) and plague keys (store in ~/.buildsys/) |
| | | |
| When they have koozali shell and buildsys access, you'll need to set up their configs | | When they have koozali shell and buildsys access, you'll need to set up their configs |
| | | |
− | For shell.koozali.org<syntaxhighlight lang="bash"> | + | =====For shell.koozali.org (cvs) ===== |
| + | <syntaxhighlight lang="bash"> |
| nano ~/.ssh/config | | nano ~/.ssh/config |
| | | |
Line 101: |
Line 106: |
| </syntaxhighlight>If you didn't have an existing ~/.ssh/config file you may need to change the permissions<syntaxhighlight lang="bash"> | | </syntaxhighlight>If you didn't have an existing ~/.ssh/config file you may need to change the permissions<syntaxhighlight lang="bash"> |
| chmod 0600 ~/.ssh/config | | chmod 0600 ~/.ssh/config |
− | </syntaxhighlight>For buildsys<syntaxhighlight lang="bash"> | + | </syntaxhighlight> |
| + | |
| + | =====For buildsys===== |
| + | <syntaxhighlight lang="bash"> |
| nano ~/.plague-client.cfg | | nano ~/.plague-client.cfg |
| | | |
Line 134: |
Line 142: |
| build32-1.contribs.org i386 i486 i586 i686 athlon noarch available | | build32-1.contribs.org i386 i486 i586 i686 athlon noarch available |
| | | |
− |
| + | ===== For src.koozali.org (git)===== |
| + | |
| + | |
| [[Category:Developer]] | | [[Category:Developer]] |