Ok,
so then I have multilib
I runned ebuild gcc-3.4.3-r1.ebuild unpack
and I saw that the if is_multilib part was executed.
so, no risk re-emerging gcc
but as (if I understand correctly (being less smart than other :-( )) we
have multilib support without multilib USE flag
emerge will not remerge (with --newuse) affected packages and you have
to re-emerge them yourself, and it looks that dependencies don't work
either (see previous mail)
so maybe portage has to be fixed to handle this.
Pascal
Simon Stelling wrote:
>Hi,
>
>It looks like some users are a bit confused about the new 2005.0 profile
>and multilib, so I'll give a little statement ;)
>
>AFAIK, there is no mechanism to force a specific use flag with a
>profile. However, we want to force 'multilib' on the normal 2005.0
>profile, so we (i.e. eradicator) did the following:
>
>/usr/portage/profiles/default-linux/amd64/2005.0/use.mask:
># Jeremy Huddleston <[EMAIL PROTECTED]>
># multilib is forced on when we have ${MULTILIB_ABIS} defined
>multilib
>
>/usr/portage/profiles/default-linux/amd64/2005.0/make.defaults:
>...
>MULTILIB_ABIS="x86 amd64"
>DEFAULT_ABI="amd64"
>...
>
>This means that we disabled the 'multilib' use flag because you no
>longer have the choice (well, you have the choice to switch to
>2005.0/no-multilib, but that's another point ;)) to enable/disable
>multilib support for your packages, they ALWAYS will be
>multilib-enabled. The star in (-multilib)* is quite logic then: you had
>the use flag on before, now the flag/your choice is disabled.
>
>I hope that helps to clear up misunderstandings.
>
>Greetings,
>
>blubb
>
>--
>[email protected] mailing list
>
>
>
--
[email protected] mailing list
