Difference between revisions of "SME Server:Documentation:Developers Manual:Section5"

From SME Server
Jump to navigationJump to search
Line 5: Line 5:
 
===OVERVIEW===
 
===OVERVIEW===
  
The SME Server update and maintenance cycle consists in the management of a number of repositories and package categories.
+
The SME Server update and maintenance cycle consists in the management of a number of repositories and package categories.
 
 
====Repositories====
 
The master directories associated with the update and maintenance cycles are located on the build system. Their content is then propagated to the mirrors.
 
 
 
They are:
 
-dev [corresponds to smedev in the mirrors]
 
-test [corresponds to smetest in the mirrors]
 
-updates-testing [corresponds to smeupdates-testing in the mirrors]
 
-updates [corresponds to smeupdates in the mirrors]
 
 
 
In addition, there is a staging area (stage) that is used to build the next ISO, you will see reference to it in some repository update emails.
 

Revision as of 15:19, 2 December 2012


Other sources of information

Perl modules

If you are not already familiar with the Perl programming language, you will need to read up on at least the basics. One online course is available from http://sourceforge.net/projects/spork.

The SME Server has a wealth of Perl libraries to perform common functions including manipulating the configuration database, performing common CGI tasks, etc. The modules available include:

  • esmith::ConfigDB
  • esmith::AccountsDB
  • esmith::NetworksDB
  • esmith::HostsDB
  • esmith::NetworkServicesDB
  • esmith::DB
  • esmith::FormMagick
  • CGI::FormMagick
  • Text::Template

The following libraries are also installed for compatibility with older code, but they should no longer be used. These libraries may be removed in future releases.

  • esmith::util (deprecated)
  • esmith::db (deprecated)
  • esmith::cgi (deprecated)

The documentation can be accessed from the Linux command line on your SME Server by typing perldoc esmith::ConfigDB (or whatever module name you're interested in).

More information about building RPMs can be found at http://www.rpm.org/wiki/Docs#PackagerDocumentation. This is especially recommended if you wish to use anything more than the extremely simple outline given above. For instance, you may wish to to build RPMs using original source and patches or include more detail and functionality in your spec file.

Documentation Links

 -Managing Software with Yum - http://mirror.centos.org/centos/4/docs/html/yum/
 -CentOS 4/RHEL4 Documentation - http://mirror.centos.org/centos/4/docs/
 -Fedora Documentation - http://fedora.redhat.com/docs/
 -Fedora Developers Guide - http://fedora.redhat.com/docs/developers-guide/
 -Fedora Documentation Guide - http://fedora.redhat.com/docs/documentation-guide/
 -Maximum RPM Book - http://www.rpm.org/max-rpm-snapshot/
 -Fedora RPM Guide (draft) - http://fedora.redhat.com/docs/drafts/rpm-guide-en/
 -Fedora Wiki - Building Packages Guide - http://fedoraproject.org/wiki/Docs/Drafts/BuildingPackagesGuide
 -Fedoraproject.org RPM Packaging Guidelines - http://fedoraproject.org/wiki/PackagingGuidelines
 -Fedoraproject.org Package Review Guidelines - http://fedoraproject.org/wiki/PackageReviewGuidelines
 -Fedoraproject.org RPM Spec File Scriptlet Snippets - http://fedoraproject.org/wiki/ScriptletSnippets

Procedures for Updating, testing and releasing packages and core updates

OVERVIEW

The SME Server update and maintenance cycle consists in the management of a number of repositories and package categories.