[patch] hb-guide-ebuild.xml.patch

hb-guide-ebuild.xml.patch (text/plain), 1.75 KB, created by Julian Ospald on 2012-05-26 18:25:34 UTC

From: Julian Ospald <[e-mail]>
Date: Sat May 26 17:53:09 UTC 2012
Subject: Ebuild HOWTO

clarify handling of binary files in portage by removing needless sections
wrt bug #417535

--- gentoo-projects/www-redesign/htdocs/proj/en/devrel/handbook/hb-guide-ebuild.xml
+++ gentoo-projects/www-redesign/htdocs/proj/en/devrel/handbook/hb-guide-ebuild.xml
@@ -74,24 +74,10 @@
 Exceptions to this rule are for larger patch files (we recommend this for patches
 above 20KB) which should be put onto the Gentoo mirrors so that people
 do not waste excessive amounts of bandwidth and hard drive
-space. Also, you should not add binary (non-ASCII) files to the
-Portage CVS tree. If you need to do this in another CVS tree, for
-example, if you need to add a small PNG graphic for whatever reason,
-be sure to add it to CVS by using the <c>-kb</c> option, like so:
-</p>
-
-<pre caption="Adding binary files to CVS">
-# <i>cvs add -kb myphoto.png</i>
-</pre>
-
-<p>
-The <c>-kb</c> option tells CVS that <path>myphoto.png</path> is a binary
-file and should be treated specially.  For example, merging the 
-differences between two different versions of this file should not be 
-allowed to happen, for obvious reasons.  Also, speaking of merging 
-changes, any patches you add to Portage should generally <e>not</e> be 
-compressed.  This will allow CVS to merge changes and correctly inform 
-developers of conflicts.
+space. Also, you should <e>never</e> add binary (non-ASCII) files to the
+Portage CVS tree. Any patches you add to Portage should generally <e>not</e> be
+compressed. This will allow CVS to merge changes and correctly inform developers
+of conflicts.
 </p>
 
 <p>
@@ -2239,4 +2225,4 @@
 </body>
 </subsection>
 </section>
-</sections>
\ No newline at end of file
+</sections>