From: "Joshua Saddler (nightmorph)" <nightmorph@gentoo.org>
To: gentoo-doc-cvs@lists.gentoo.org
Subject: [gentoo-doc-cvs] gentoo commit in xml/htdocs/doc/en: quick-samba-howto.xml
Date: Wed, 2 Mar 2011 09:19:56 +0000 (UTC) [thread overview]
Message-ID: <20110302091956.1A7D520054@flycatcher.gentoo.org> (raw)
nightmorph 11/03/02 09:19:56
Modified: quick-samba-howto.xml
Log:
remove outdated keywording instructions, since the package is marked stable
Revision Changes Path
1.42 xml/htdocs/doc/en/quick-samba-howto.xml
file : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/quick-samba-howto.xml?rev=1.42&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/quick-samba-howto.xml?rev=1.42&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo/xml/htdocs/doc/en/quick-samba-howto.xml?r1=1.41&r2=1.42
Index: quick-samba-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/quick-samba-howto.xml,v
retrieving revision 1.41
retrieving revision 1.42
diff -u -r1.41 -r1.42
--- quick-samba-howto.xml 26 Jan 2009 07:30:42 -0000 1.41
+++ quick-samba-howto.xml 2 Mar 2011 09:19:55 -0000 1.42
@@ -1,9 +1,8 @@
<?xml version='1.0' encoding='UTF-8'?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/quick-samba-howto.xml,v 1.41 2009/01/26 07:30:42 nightmorph Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/quick-samba-howto.xml,v 1.42 2011/03/02 09:19:55 nightmorph Exp $ -->
-<guide link="/doc/en/quick-samba-howto.xml">
-
+<guide>
<title>Gentoo Samba3/CUPS HOWTO</title>
<author title="Author">
@@ -25,8 +24,8 @@
<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
<license/>
-<version>1.26</version>
-<date>2009-01-25</date>
+<version>2</version>
+<date>2011-03-02</date>
<chapter>
<title>Introduction to this HOWTO</title>
@@ -643,13 +642,11 @@
which can be obtained from <uri
link="http://www.adobe.com/support/downloads/main.html">Adobe</uri> (PostScript
printer drivers). Second, there are the CUPS PS drivers, to be obtained by
-emerging <c>net-print/cups-windows</c>. Note that it may still be marked ~arch,
-so you may need to add it to <path>/etc/portage/package.keywords</path>. There
-doesn't seem to be a difference between the functionality of the two, but the
-Adobe PS drivers need to be extracted on a Windows System since it's a Windows
-binary. Also the whole procedure of finding and copying the correct files is a
-bit more hassle. The CUPS drivers support some options the Adobe drivers
-don't.
+emerging <c>net-print/cups-windows</c>. There doesn't seem to be a difference
+between the functionality of the two, but the Adobe PS drivers need to be
+extracted on a Windows System since it's a Windows binary. Also the whole
+procedure of finding and copying the correct files is a bit more hassle. The
+CUPS drivers support some options the Adobe drivers don't.
</p>
<p>
next reply other threads:[~2011-03-02 9:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-02 9:19 Joshua Saddler (nightmorph) [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-07-27 2:25 [gentoo-doc-cvs] gentoo commit in xml/htdocs/doc/en: quick-samba-howto.xml Joshua Saddler (nightmorph)
2009-01-26 7:30 Joshua Saddler (nightmorph)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110302091956.1A7D520054@flycatcher.gentoo.org \
--to=nightmorph@gentoo.org \
--cc=docs-team@lists.gentoo.org \
--cc=gentoo-doc-cvs@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox