cvs commit: www/patches submit.html

jeroen at linuxfromscratch.org jeroen at linuxfromscratch.org
Tue Jun 8 01:41:29 PDT 2004


jeroen      04/06/08 02:41:29

  Modified:    patches  submit.html
  Log:
  Update the patches naming scheme on the website
  
  Revision  Changes    Path
  1.27      +2 -2      www/patches/submit.html
  
  Index: submit.html
  ===================================================================
  RCS file: /home/cvsroot/www/patches/submit.html,v
  retrieving revision 1.26
  retrieving revision 1.27
  diff -u -r1.26 -r1.27
  --- submit.html	21 Mar 2004 22:10:30 -0000	1.26
  +++ submit.html	8 Jun 2004 08:41:29 -0000	1.27
  @@ -64,13 +64,13 @@
   		<p><code>${packageName}-${packageVersion}-${patchName}-${patchVersion}.patch</code></p>
   		<dl>
   			<dt>packageName</dt>
  -				<dd>Official name of the package. Be sure to follow the same capitalization that is followed by the official tarball for the package.</dd>
  +				<dd>Official name of the package. Be sure to follow the same capitalization that is followed by the official tarball for the package (i.e. cracklib would be cracklib,2.7, gcc would be gcc-3.3.4, etc.). changing conventions (e.g. ',' or '-' or differing package names) shouldn't be a consideration - it's up to upstream how they package their tarballs and we should reflect their naming convention. Where package descriptions have multiple words, those words should be '_' separated to differentiate between the '-' separated fields we have on the patches project at present.</dd>
   			<dt>packageVersion</dt>
   				<dd>Version against which the patch applies.</dd>
   			<dt>patchName</dt>
   				<dd>Short name for the patch (also include architecture if the patch is for a particular architecture.</dd>
   			<dt>patchVersion</dt>
  -				<dd>Version of the patch (usually 1). This field is optional.</dd>
  +				<dd>Version of the patch (starting at 1, if there is no previous version). This field is mandatory.</dd>
   		</dl>
   	</li>
   	<li>
  
  
  



More information about the website mailing list