From: Sebastian Pipping <sping@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] catalyst's ccache USE flag seems a bit stupid
Date: Sat, 25 Jun 2011 16:37:28 +0200 [thread overview]
Message-ID: <4E05F2A8.7070200@gentoo.org> (raw)
In-Reply-To: <BANLkTikPfGY-H+rfMaBPfvWptMziHxThYQ@mail.gmail.com>
On 06/25/2011 05:55 AM, Matt Turner wrote:
> I might suggest removing all ccache-related stuff in the ebuild and
> adding a few einfo lines to the ebuild suggesting to the user to
> emerge ccache (so that it'll be in @world) and how to modify
> catalyst.conf to enable it. Do you think that would be OK?
>
> It just seems like the USE flag is the wrong way of doing this.
I don't know. dev-util/metro seems to pull in ccache in a similar way.
I would love to hear a third voice on this.
> (I'm so glad to see you working on catalyst. I've got a number of
> patches that I need to commit, especially now that I see some other
> activity)
Please go ahead.
Best,
Sebastian
prev parent reply other threads:[~2011-06-25 14:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-25 2:07 [gentoo-catalyst] catalyst's ccache USE flag seems a bit stupid Matt Turner
2011-06-25 2:17 ` Sebastian Pipping
2011-06-25 3:55 ` Matt Turner
2011-06-25 14:37 ` Sebastian Pipping [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=4E05F2A8.7070200@gentoo.org \
--to=sping@gentoo.org \
--cc=gentoo-catalyst@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