Changes

From SME Server
Jump to navigationJump to search

SME Server:Documentation:Developers Manual:Chapter14 (view source)

Revision as of 02:59, 12 March 2020

467 bytes removed ,  02:59, 12 March 2020
→‎Configuring your development environment
Line 6: Line 6:  
===Configuring your development environment===
 
===Configuring your development environment===
   −
The SME Server source code is checked into CVS at SourceForge.  
+
The SME Server source code is checked into CVS at koozali.org.  
−
SME Server code is stored in the CVS on http://www.sourceforge.net in two repositories:
+
SME Server code is stored in the CVS on shell.koozali.org in two repositories:
−
* [http://fisheye1.cenqua.com/browse/smeserver/ CVS SME Server] which holds the core packages of the SME Server
+
* [https://viewvc.koozali.org/smeserver/ CVS SME Server] which holds the core packages of the SME Server
−
* [http://fisheye1.cenqua.com/browse/smecontribs/ CVS SME Contribs] which holds the contribs packages
+
* [https://viewvc.koozali.org/smecontribs/ CVS SME Contribs] which holds the contribs packages
    
Reminder:  
 
Reminder:  
 
The SME Server source code is released under the GPL. You must release the source code to all modifications. If you make improvements, please raise a bug and attach a patch so the change can be discussed and pulled back into the base for everyone to share.
 
The SME Server source code is released under the GPL. You must release the source code to all modifications. If you make improvements, please raise a bug and attach a patch so the change can be discussed and pulled back into the base for everyone to share.
   −
Only developers who are going to put patches back into CVS and build new packages need SourceForge CVS access. The sources are freely available and patches are gratefully received. Just follow the instructions in this section and attach the patch(es) to the Bugzilla entry, explaining why the change should be made.
+
Only developers who are going to put patches back into CVS and build new packages need shell.koozali.org CVS access. The sources are freely available and patches are gratefully received. Just follow the instructions in this section and attach the patch(es) to the Bugzilla entry, explaining why the change should be made.
    
</div><div class="SECT2">
 
</div><div class="SECT2">
Line 66: Line 66:  
   build32-1.contribs.org      i386 i486 i586 i686 athlon noarch  available
 
   build32-1.contribs.org      i386 i486 i586 i686 athlon noarch  available
   −
====Sourceforge access====
+
====CVS shell.koozali.org access====
−
* SME Server code is stored in the CVS on  http://SourceForge.net. To be able to work on your code in the SME Server CVS repository you need an account on SourceForge. With this account the development team can give you access to the CVS repository. More information can be found here:
+
* SME Server code is stored in the CVS on  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.
−
[http://sourceforge.net/apps/trac/sourceforge/wiki/Register%20a%20user%20account Registering a User Account]
  −
[http://sourceforge.net/apps/trac/sourceforge/wiki/CVS CVS (Version Control for Source Code)]
  −
[http://sourceforge.net/apps/trac/sourceforge/wiki/SSH%20keys SSH Key Generation and Usage]
     −
* After you have created your SourceForge account 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.
   −
* Links to manage your SSH keys on SourceForge may be found on the [http://sourceforge.net/account/services SourceForge Account Services page].
+
* If local username is different to shell.koozali.org username edit ~/.ssh/config:
−
 
  −
* If local username is different to sf.net username edit ~/.ssh/config:
   
   
 
   
−
  Host  smeserver.cvs.sourceforge.net
+
  Host  shell.koozali.org
−
  User  sfusername ''(without @shell.sf.net)''
+
  User  koozaliusername ''(without @shell.koozali.org)''
−
  Host  smecontribs.cvs.sourceforge.net
+
  port 222
−
User  sfusername ''(without @shell.sf.net)''
      
* Don't forget to set the proper privileges on the file
 
* Don't forget to set the proper privileges on the file
Line 87: Line 81:  
  chmod 600 ~/.ssh/config
 
  chmod 600 ~/.ssh/config
   −
====Import source to sourceforge====
+
====Import source to shell.koozali.org====
−
Email admin@contribs.org with the location of your rpm, it will be imported into the build system for you. Follow the same procedure when an upstrean release occurs, eg a new .tar.gz, Update your local cvs with:
+
Email admin@contribs.org with the location of your rpm, it will be imported into the build system for you. Follow the same procedure when an upstream release occurs, eg a new .tar.gz, Update your local cvs with:
    
  cvs update -dPA
 
  cvs update -dPA
 +
 +
If you have developer access to buildsys you can follow this guide
 +
 +
https://wiki.contribs.org/Package_Import
    
====Import cvs in your workspace====
 
====Import cvs in your workspace====
Line 97: Line 95:  
  mkdir ~/home/smeserver
 
  mkdir ~/home/smeserver
 
  cd ~/home/smeserver
 
  cd ~/home/smeserver
−
  cvs -z3 -d:ext:smeserver.cvs.sourceforge.net:/cvsroot/smeserver co -P rpms  
+
  cvs -z3 -d:ext:shell.koozali.org:/cvs/smeserver co -P rpms  
    
  mkdir ~/home/smecontribs
 
  mkdir ~/home/smecontribs
 
  cd ~/home/smecontribs  
 
  cd ~/home/smecontribs  
−
  cvs -z3 -d:ext:smecontribs.cvs.sourceforge.net:/cvsroot/smecontribs co -P rpms  
+
  cvs -z3 -d:ext:shell.koozali.org:/cvs/smecontribs co -P rpms  
 
   
 
   
 
To refresh run the following from the rpms directory, or any lower directory with a CVS dir
 
To refresh run the following from the rpms directory, or any lower directory with a CVS dir
Line 135: Line 133:  
and so, we want to modify the <tt class="FILENAME">smeserver-yum</tt> package.
 
and so, we want to modify the <tt class="FILENAME">smeserver-yum</tt> package.
   −
<span class="emphasis">''All packages on the SME Server ISO/CD must be checked into SourceForge CVS''</span>. The only exceptions are packages which come from the following upstream repositories: CentOS and dag.
+
<span class="emphasis">''All packages on the SME Server ISO/CD must be checked into shell.koozali.org CVS''</span>. The only exceptions are packages which come from the following upstream repositories: CentOS and dag.
    
</div><div class="SECT2">
 
</div><div class="SECT2">
 
----
 
----
   −
You can now retrieve one of the packages from SourceForge. In this case, we want to modify the <var class="LITERAL">smeserver-yum</var> package, so let's retrieve it from SourceForge:
+
You can now retrieve one of the packages from shell.koozali.org. In this case, we want to modify the <var class="LITERAL">smeserver-yum</var> package, so let's retrieve it from shell.koozali.org:
   −
  cvs -z3 -d:ext:smeserver.cvs.sourceforge.net:/cvsroot/smeserver co -P smeserver-yum
+
  cvs -z3 -d:ext:shell.koozali.org:/cvs/smeserver co -P smeserver-yum
    
Change to work directory
 
Change to work directory
Unnilennium
Super Admin, Wiki & Docs Team, Bureaucrats, Interface administrators, Administrators
3,250

edits

Retrieved from "https://wiki.koozali.org/Special:MobileDiff/30648...38335"

Navigation menu