From: "W. Trevor King" <wking@tremily.us>
To: gentoo-catalyst@lists.gentoo.org
Subject: [gentoo-catalyst] Re: make catalyst call emerge --deep
Date: Wed, 10 Apr 2013 12:16:15 -0400 [thread overview]
Message-ID: <20130410161614.GD4694@odin.tremily.us> (raw)
In-Reply-To: <51658B47.3020008@arskom.com.tr>
[-- Attachment #1: Type: text/plain, Size: 1065 bytes --]
On Wed, Apr 10, 2013 at 06:54:47PM +0300, Burak Arslan wrote:
> 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?
Are you using `update_seed: yes` in your stage1 spec? You may also
need to set update_seed_comman, since by default catalyst only updates
gcc and its dependencies. Seed updates are not super clear to me, and
there has been a good deal of talk about seed updates on the list
recently [1,2,3], so take my advice with a grain of salt ;).
Cheers,
Trevor
[1]: http://thread.gmane.org/gmane.linux.gentoo.catalyst/2137
[2]: http://thread.gmane.org/gmane.linux.gentoo.catalyst/2166
[3]: http://thread.gmane.org/gmane.linux.gentoo.catalyst/2209
--
This email may be signed or encrypted with GnuPG (http://www.gnupg.org).
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-04-10 22: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 ` W. Trevor King [this message]
2013-04-10 16:22 ` Rick "Zero_Chaos" Farina
2013-04-10 17:35 ` Matt Turner
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=20130410161614.GD4694@odin.tremily.us \
--to=wking@tremily.us \
--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