From: "Kevin F. Quinn" <kevquinn@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] distcc and precompiled headers
Date: Sat, 19 May 2007 17:38:51 +0200 [thread overview]
Message-ID: <20070519173851.7c46348f@c1358217.kevquinn.com> (raw)
In-Reply-To: <47748.192.168.2.155.1179492070.squirrel@www.aei-tech.com>
[-- Attachment #1: Type: text/plain, Size: 893 bytes --]
On Fri, 18 May 2007 08:41:10 -0400 (EDT)
"Caleb Tennis" <caleb@gentoo.org> wrote:
> Based on some recent findings, it looks like the two above mentioned
> features don't work together. pch don't get distributed to distcc
> nodes, so they're basically mutually exclusive. However, distcc is a
> FEATURE and pch are a USE flag.
>
> Should we just put a check in each ebuild that uses the pch use flag,
> make an eclass, or build something into the package manager(s) ?
> Thoughts?
I'd go with a 'pch' utility eclass, and have packages that IUSE pch add
a call in pkg_setup (which would either die, or disable distcc).
On a related note, we had a discussion on bug #128810 a while back about
whether the package manager should be doing distcc and ccache at all,
anyway. Personally I think the package manager shouldn't be involved in
that at all.
--
Kevin F. Quinn
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2007-05-19 15:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-18 12:41 [gentoo-dev] distcc and precompiled headers Caleb Tennis
2007-05-18 13:26 ` Luca Barbato
2007-05-19 6:59 ` [gentoo-dev] " Steve Long
2007-05-19 15:38 ` Kevin F. Quinn [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=20070519173851.7c46348f@c1358217.kevquinn.com \
--to=kevquinn@gentoo.org \
--cc=gentoo-dev@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