From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64] Re: CUPS now failing with "/usr/libexec/cups/filter/foomatic-rip failed"
Date: Tue, 25 Mar 2008 11:16:27 +0000 (UTC) [thread overview]
Message-ID: <pan.2008.03.25.11.16.26@cox.net> (raw)
In-Reply-To: pan.2008.03.25.11.05.06@cox.net
Duncan <1i5t5.duncan@cox.net> posted pan.2008.03.25.11.05.06@cox.net,
excerpted below, on Tue, 25 Mar 2008 11:05:07 +0000:
> You have multiple machines. Are you making use of binary packages?
> Assuming you use portage, FEATURES=buildpkg on your first upgraded
> machine, with all machines set to use the same PKGDIR and using emerge
> --usepkgonly (-K) on everything but the first one (at least where USE
> flags are the same, and assuming compatible machine and instruction
> types) should be a real boon to you.
This one's probably worth pointing out by itself. With multiple
machines, particularly all those myth client machines likely configured
virtually identically, you really /are/ wasting time if you are
rebuilding from source for each one. That's what Features=buildpkg, the
PKGDIR var, and --usepkgonly are for, after all. =8^) (I assume the
other-than-portage package managers have similar binary package features,
but wouldn't know the settings or how to invoke them.)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
--
gentoo-amd64@lists.gentoo.org mailing list
prev parent reply other threads:[~2008-03-25 11:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-24 23:25 [gentoo-amd64] CUPS now failing with "/usr/libexec/cups/filter/foomatic-rip failed" Mark Knecht
2008-03-25 1:22 ` [gentoo-amd64] " Mark Knecht
2008-03-25 3:52 ` Duncan
2008-03-25 4:45 ` Mark Knecht
2008-03-25 11:05 ` Duncan
2008-03-25 11:16 ` Duncan [this message]
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=pan.2008.03.25.11.16.26@cox.net \
--to=1i5t5.duncan@cox.net \
--cc=gentoo-amd64@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