Line 14: |
Line 14: |
| | | |
| === Installation === | | === Installation === |
− | This contrib can be found in the [http://mirror.contribs.org/smeserver/releases/7/smecontribs/i386/repodata/index.html SME Contribs] repository (available on SME Servers as of smeserver-yum-1.2.0-41).
| + | <tabs container><tab name="For SME 10"> |
| + | yum install smeserver-subversion --enablerepo=smecontribs |
| + | </tab><tab name="For SME 9"> |
| To install this contrib get shell access as root user and issue the following command: | | To install this contrib get shell access as root user and issue the following command: |
| yum install smeserver-subversion --enablerepo=smecontribs | | yum install smeserver-subversion --enablerepo=smecontribs |
| After yum has finished make sure to issue the following commands: | | After yum has finished make sure to issue the following commands: |
− | signal-event post-upgrade | + | signal-event post-upgrade ; signal-event reboot |
− | signal-event reboot
| + | or if you don't want to restart your server |
− | | + | config set UnsavedChanges no |
− | ==== '''For SME 9''' ====
| |
− | You have to enable the '''[[stephdl]]''' repository, see '''[[bugzilla:8998]]'''
| |
− | yum install --enablerepo=stephdl --enablerepo=epel smeserver-subversion | |
− | | |
− | After yum has finished make sure to issue the following commands:
| |
− | signal-event post-upgrade
| |
− | signal-event reboot
| |
| | | |
| + | </tab><tab name="For SME 8"> |
| ==== Updating the subversion 'core' ==== | | ==== Updating the subversion 'core' ==== |
| + | * only for sme8 |
| The smeserver-subversion contrib does not contain the subversion package itself, as this removes the need of releasing a new contrib every time a new subversion version is released. | | The smeserver-subversion contrib does not contain the subversion package itself, as this removes the need of releasing a new contrib every time a new subversion version is released. |
| | | |
| This contrib is meant to tie it in to SME Server. The command in the installation section will install the latest subversion version yum can find in the enabled repositories. the SME Contribs repository should contain the latest release of subversion. You can install or update like this | | This contrib is meant to tie it in to SME Server. The command in the installation section will install the latest subversion version yum can find in the enabled repositories. the SME Contribs repository should contain the latest release of subversion. You can install or update like this |
| yum update subversion --enablerepo=smecontribs | | yum update subversion --enablerepo=smecontribs |
| + | </tab> |
| + | </tabs> |
| | | |
| === Removal === | | === Removal === |
| To remove this contribution issue the following command: | | To remove this contribution issue the following command: |
| yum remove smeserver-subversion | | yum remove smeserver-subversion |
− | After yum has finished make sure to issue the following commands: | + | After yum has finished make sure to issue the following commands for SME9 and previous versions: |
| signal-event post-upgrade | | signal-event post-upgrade |
| signal-event reboot | | signal-event reboot |
Line 50: |
Line 49: |
| * Be careful when setting permissions for reading and writing to a repository. When no selections are made in both the "read-only access" lists, or both the "full access" lists, they will default to 'Everyone'. To completely restrict access to specific groups and users, you must make a selection from both the "read-only access" and the "full access" lists, for either one or more groups, or one or more users. | | * Be careful when setting permissions for reading and writing to a repository. When no selections are made in both the "read-only access" lists, or both the "full access" lists, they will default to 'Everyone'. To completely restrict access to specific groups and users, you must make a selection from both the "read-only access" and the "full access" lists, for either one or more groups, or one or more users. |
| <br> | | <br> |
− | Next procedure is to create the recommended folder structure in your repository with this command in a terminal | + | Next procedure is to create the recommended folder structure in your repository with this command in a terminal (just a recommendation and not nessesary) |
| <nowiki>svn mkdir https://server-name/repository-name/{branches,tags,trunk} -m "Recommended structure"</nowiki> | | <nowiki>svn mkdir https://server-name/repository-name/{branches,tags,trunk} -m "Recommended structure"</nowiki> |
| | | |
Line 75: |
Line 74: |
| # Commit your changes to the repository. Go to step 2. | | # Commit your changes to the repository. Go to step 2. |
| <br> | | <br> |
− | To work with your repository you need to use a client like TortoiseSVN for Windows or RabbitVCS for Linux. ALso possible to use the command line with the svn command. You just import your code to <nowiki>https://server-name/repository-name/trunk</nowiki> | + | To work with your repository you need to use a client like TortoiseSVN for Windows or RabbitVCS for Linux. ALso possible to use the command line with the svn command. You just import your code to <nowiki>https://server-name/repository-name/trunk</nowiki><br> |
| | | |
| === Additional information === | | === Additional information === |