From: Max Arnold <lwarxx@gmail.com>
To: gentoo-catalyst@lists.gentoo.org
Subject: [gentoo-catalyst] proper way to deviate in system use flags?
Date: Fri, 18 Apr 2008 11:29:29 +0800 [thread overview]
Message-ID: <20080418032929.GC30602@dev.local> (raw)
Hello all!
I'm trying to build my own stage4 with specific packages and use flags.
My steps are: stage3-i686-2007.0 + recent snapshot -> stage1 -> stage2 -> stage3 -> stage4
Specs for stages 1-3 are generic (just copied from releng/specs/2007.0/x86), and stage4
adds portage_confdir, stage4/use and several packages.
Stage4 compiles fine, but when I chroot to it and issue emerge -pvuDN world, portage
wants to remerge several system packages due to changed use flags (for example ipv6, which
is disabled in my stage4/use).
So it is seems that my stage4/use and portage_confdir does not affect system packages
(I guess that catalyst does only --emptytree when emerging stage4).
So, there are my questions:
1. Am I correct in assumption that use flags are stacked during stage4 like this:
profile -> stage4/use -> package.use (increasing priority from left to right)?
2. What is the proper (and simple to maintain) way to deviate slightly in system use flags?
My guesses:
1. Add 'hostuse' variable to earlier specs (stage3?)
2. Add 'portage_confdir' to earlier specs (but my -ipv6 listed in stage4/use and not in package.use)
3. Create new target (based on stage4 code) and add --newuse somewhere
4. Create my own profile (don't know where to put it and how to maintain during tree updates)
Any suggestions?
--
gentoo-catalyst@lists.gentoo.org mailing list
next reply other threads:[~2008-04-18 3:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-18 3:29 Max Arnold [this message]
2008-04-18 22:12 ` [gentoo-catalyst] proper way to deviate in system use flags? Chris Gianelloni
2008-04-19 3:19 ` Max Arnold
2008-04-21 15:32 ` Chris Gianelloni
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=20080418032929.GC30602@dev.local \
--to=lwarxx@gmail.com \
--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