neysx       05/11/21 15:44:17

  Modified:    xml/htdocs/doc/en printing-howto.xml
  Log:
  #110771 Make it more obvious that the ppds USE flag is required for hplip

Revision  Changes    Path
1.53      +12 -3     xml/htdocs/doc/en/printing-howto.xml

file : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/printing-howto.xml?rev=1.53&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/printing-howto.xml?rev=1.53&content-type=text/plain&cvsroot=gentoo
diff : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/printing-howto.xml.diff?r1=1.52&r2=1.53&cvsroot=gentoo

Index: printing-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/printing-howto.xml,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -r1.52 -r1.53
--- printing-howto.xml  5 Nov 2005 17:29:16 -0000       1.52
+++ printing-howto.xml  21 Nov 2005 15:44:17 -0000      1.53
@@ -1,6 +1,6 @@
 <?xml version='1.0' encoding="UTF-8"?>
 
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/printing-howto.xml,v 1.52 
2005/11/05 17:29:16 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/printing-howto.xml,v 1.53 
2005/11/21 15:44:17 neysx Exp $ -->
 
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 
@@ -21,8 +21,8 @@
 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 <license/>
 
-<version>2.3</version>
-<date>2005-11-05</date>
+<version>2.4</version>
+<date>2005-11-21</date>
 
 <chapter>
 <title>Printing and Gentoo Linux</title>
@@ -758,6 +758,15 @@
 </p>
 
 <pre caption="Installing the hplip drivers">
+<comment>(Check that the ppds USE flag is enabled)</comment>
+# <i>emerge -vp hplip</i>
+These are the packages that I would merge, in order:
+
+Calculating dependencies ...done!
+[ebuild  N    ] net-print/hplip-0.9.5  +X +cups +foomaticdb 
<comment>+ppds</comment> -qt -scanner -snmp +usb 9,255 kB 
+
+Total size of downloads: 9,255 kB
+
 # <i>emerge hplip</i>
 </pre>
 



-- 
[email protected] mailing list

Reply via email to