nightmorph    08/12/24 07:07:48

  Modified:             hb-working-portage.xml
  Log:
  users shouldn't try running ebuild foo digest anyway. digests haven't been 
used in a year, ever since the tree was converted to manifest2. the correct 
command is ebuild foo manifest, so fixed in the example of what not to do.

Revision  Changes    Path
1.72                 xml/htdocs/doc/en/handbook/hb-working-portage.xml

file : 
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-working-portage.xml?rev=1.72&view=markup
plain: 
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-working-portage.xml?rev=1.72&content-type=text/plain
diff : 
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/handbook/hb-working-portage.xml?r1=1.71&r2=1.72

Index: hb-working-portage.xml
===================================================================
RCS file: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-working-portage.xml,v
retrieving revision 1.71
retrieving revision 1.72
diff -u -r1.71 -r1.72
--- hb-working-portage.xml      1 Mar 2008 07:16:57 -0000       1.71
+++ hb-working-portage.xml      24 Dec 2008 07:07:48 -0000      1.72
@@ -4,7 +4,7 @@
 <!-- The content of this document is licensed under the CC-BY-SA license -->
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 
-<!-- $Header: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-working-portage.xml,v 1.71 
2008/03/01 07:16:57 nightmorph Exp $ -->
+<!-- $Header: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/hb-working-portage.xml,v 1.72 
2008/12/24 07:07:48 nightmorph Exp $ -->
 
 <sections>
 
@@ -13,8 +13,8 @@
 maintain the software on his system.
 </abstract>
 
-<version>1.64</version>
-<date>2008-02-29</date>
+<version>1.65</version>
+<date>2008-12-23</date>
 
 <section>
 <title>Welcome to Portage</title>
@@ -647,7 +647,7 @@
 
 <p>
 When the digest verification fails, do <e>not</e> try to re-digest the package
-yourself. Running <c>ebuild foo digest</c> will not fix the problem; it will
+yourself. Running <c>ebuild foo manifest</c> will not fix the problem; it will
 almost certainly make it worse!
 </p>
 




Reply via email to