On Fri, 8 Oct 2004 10:22:00 +0200 Spider <spider@gentoo.org> wrote:
| begin quote
| On Thu, 7 Oct 2004 20:09:51 -0700 (PDT)
| Dustin <laurence@alice.caltech.edu> wrote:
|
| > > Yup, probably best. The defaults are reasonably sane, though. Note
| > > that you can't safely change USE flags after bootstrapping (except
| > > where you can or where you get lucky).
| >
| > Urk. Really? Did I just miss the place where this was explained?
| > Seems like I've seen much advice that involved just this.
|
| He's mostly talking hot air.
No, I'm really not. See, for example, the acl bug that was making
certain systems break because of a change in USE flags between stages
and the live system.
| The other case where things may break is in second-line dependencies.
| at this point, baz may break due to having things torn away from
| beneath it. suggested is to use "revdep-rebuild" in cases like this,
| but,
| this is only the case when applications and libraries are badly
| designed and expose inherited symbols downwards. Could happen, but
| really shouldn't.
revdep-rebuild will not catch all of these. The correct solution would
be to use the DEPEND="foo/bar[baz]" syntax, but since Nick doesn't care
about this it probably won't ever get implemented correctly. It's not
necessarily a library design problem either, there're totally sane and
legitimate places where this can crop up.
Really, if you think it's not an issue, try tinkering with pam, acl or
multilib sometime. It's a great way to totally screw up a system, and
part of the reason you can't mix binaries from systems with different
make.conf entries.
--
Ciaran McCreesh : Gentoo Developer (Sparc, MIPS, Vim, Fluxbox)
Mail : ciaranm at gentoo.org
Web :
http://dev.gentoo.org/~ciaranm