From: Matt Turner <mattst88@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] make catalyst call emerge --deep
Date: Wed, 10 Apr 2013 10:35:04 -0700 [thread overview]
Message-ID: <CAEdQ38Hukhj2zwVhw__vvp+VkTS2LTVsWgre5P+LP+p-jnDdqQ@mail.gmail.com> (raw)
In-Reply-To: <51658B47.3020008@arskom.com.tr>
On Wed, Apr 10, 2013 at 8:54 AM, Burak Arslan
<burak.arslan@arskom.com.tr> wrote:
> Hi,
>
> In a build (a desktop stage 4) I'm trying to run, I'm getting multiple udevs
> (=197-r1 and >=197-r2) pulled in (among other errors, see below). My
> impression is that if I were able to pass --deep to emerge command, it'd
> just go through. Is there a non-hacky way of doing this?
Modify catalyst and try it. We should confirm that --deep actually
would fix this problem before deciding it's the solution.
If it is, I'm all for adding it.
next prev parent reply other threads:[~2013-04-10 17:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-10 15:54 [gentoo-catalyst] make catalyst call emerge --deep Burak Arslan
2013-04-10 16:16 ` [gentoo-catalyst] " W. Trevor King
2013-04-10 16:22 ` [gentoo-catalyst] " Rick "Zero_Chaos" Farina
2013-04-10 17:35 ` Matt Turner [this message]
2013-04-10 19:41 ` Rick "Zero_Chaos" Farina
2013-04-11 4:42 ` Peter Stuge
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=CAEdQ38Hukhj2zwVhw__vvp+VkTS2LTVsWgre5P+LP+p-jnDdqQ@mail.gmail.com \
--to=mattst88@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