Changes

It is a good idea to perform all of your checkouts in a standard directory hierarchy. This makes it easier to move around between the packages. On a shared build server, it also makes it easier for people to recover your work if required (for example when you are on holidays). If you want to use filesharing to edit files from a networked PC, you might like to use <tt class="FILENAME">~/home/smeserver/</tt>. On a shared build server, you might even use something like <tt class="FILENAME">/builds/users/$LOGNAME/smeserver/</tt> so the files are not in your home directory and are accessible to all developers.

It is a good idea to perform all of your checkouts in a standard directory hierarchy. This makes it easier to move around between the packages. On a shared build server, it also makes it easier for people to recover your work if required (for example when you are on holidays). If you want to use filesharing to edit files from a networked PC, you might like to use <tt class="FILENAME">~/home/smeserver/</tt>. On a shared build server, you might even use something like <tt class="FILENAME">/builds/users/$LOGNAME/smeserver/</tt> so the files are not in your home directory and are accessible to all developers.

 

{{Note box|msg=Reminder: All files must be checked in using Unix text format.}}

<div class="NOTE"><blockquote class="NOTE">

 

'''Note: '''Reminder: All files must be checked in using Unix text format.

 

  [gordonr@smebuild ~]$ mkdir ~/smeserver

  [gordonr@smebuild ~]$ mkdir ~/smeserver

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.

 

{{Note box|msg=You can view a complete list of the packages checked into SourceForge CVS http://smeserver.cvs.sourceforge.net/smeserver/. On rare occasions, the sources of particular packages may be slightly out of date as there is a small delay (typically only a few hours) between changes to the developer CVS and the anonymous CVS. In practice, this rarely matters and at worst it requires a merging of your changes with any other recent changes to the package.}}

<div class="NOTE"><blockquote class="NOTE">

 

'''Note: '''You can view a complete list of the packages checked into SourceForge CVS http://smeserver.cvs.sourceforge.net/smeserver/. On rare occasions, the sources of particular packages may be slightly out of date as there is a small delay (typically only a few hours) between changes to the developer CVS and the anonymous CVS. In practice, this rarely matters and at worst it requires a merging of your changes with any other recent changes to the 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 SourceForge CVS''</span>. The only exceptions are packages which come from the following upstream repositories: CentOS and dag.

  U smeserver-yum/P/smeserver-yum-1.2.0-ModifyUpdateDBs.patch

  U smeserver-yum/P/smeserver-yum-1.2.0-ModifyUpdateDBs.patch

  U smeserver-yum/S/smeserver-yum-1.2.0.tar.gz

  U smeserver-yum/S/smeserver-yum-1.2.0.tar.gz

 

{{Note box|msg=Use '''mzgetsf''' if you have a SME Server developer account.}}

<div class="NOTE"><blockquote class="NOTE">

</div><div class="SECT2">

 

'''Note: '''Use '''mzgetsf''' if you have a SME Server developer account.

 

</blockquote></div></div><div class="SECT2">

----

----

* The <tt class="FILENAME">S</tt> directory contains the source tarball(s): [gordonr@smebuild smeserver-yum]$ ls S

* The <tt class="FILENAME">S</tt> directory contains the source tarball(s): [gordonr@smebuild smeserver-yum]$ ls S

  CVS  smeserver-yum-1.2.0.tar.gz

  CVS  smeserver-yum-1.2.0.tar.gz

{{Note box|msg=The <tt class="FILENAME">smeserver-yum</tt> subdirectory is a leftover from an incorrect package import. It can be ignored and will be removed when maintenance is next performed on the CVS repository.}}

 

</div><div class="SECT2">

<div class="NOTE"><blockquote class="NOTE">

 

'''Note: '''The <tt class="FILENAME">smeserver-yum</tt> subdirectory is a leftover from an incorrect package import. It can be ignored and will be removed when maintenance is next performed on the CVS repository.

 

</blockquote></div></div><div class="SECT2">

----

----

Mezzanine automates the creation of patches through the '''mzpatch''' command.

Mezzanine automates the creation of patches through the '''mzpatch''' command.

 

{{Note box|msg=Always run '''mzpatch''' from the top-level directory of your package (e.g. <tt class="FILENAME">~/smeserver/smeserver-yum/</tt>).}}

<div class="NOTE"><blockquote class="NOTE">

 

'''Note: '''Always run '''mzpatch''' from the top-level directory of your package (e.g. <tt class="FILENAME">~/smeserver/smeserver-yum/</tt>).

 

  [gordonr@smebuild actions]$ cd ~/smeserver/smeserver-yum/

  [gordonr@smebuild actions]$ cd ~/smeserver/smeserver-yum/

If you haven't fixed the bug, repeat the cycle: make changes, build a new patch, update the release number (e.g. to 05ff02, 05ff03, etc.), build a new package, test. Don't worry about using up release numbers.

If you haven't fixed the bug, repeat the cycle: make changes, build a new patch, update the release number (e.g. to 05ff02, 05ff03, etc.), build a new package, test. Don't worry about using up release numbers.

 

{{Note box|msg=Actually fixing bug 1174 is left as an exercise for the reader. Fame and fortune (or at least thanks) await the person who does.}}

<div class="NOTE"><blockquote class="NOTE">

</div><div class="SECT2">

 

'''Note: '''Actually fixing bug 1174 is left as an exercise for the reader. Fame and fortune (or at least thanks) await the person who does.

 

</blockquote></div></div><div class="SECT2">

----

----