1 |
On Monday 13 July 2009 09:11:04 Helmut Jarausch wrote: |
2 |
> Hi, |
3 |
> |
4 |
> would anybody please be so kind to explain to me how |
5 |
> emerge --update --newuse --deep @system @world |
6 |
> works. |
7 |
> |
8 |
> E.g. it wants to re-emerge sys-devel/gcc because of the |
9 |
> "new use flag nptl" according to |
10 |
> |
11 |
> [ebuild R ] sys-devel/gcc-4.4.0 USE="nptl%*" |
12 |
> [ebuild R ] sys-devel/gcc-4.3.3-r2 USE="nptl%*" |
13 |
> |
14 |
> But, looking at the corresponding ebuild files they don't |
15 |
> use (IUSE or other) such a use flag. |
16 |
> But why then does emerge want to rebuild those packages.? |
17 |
> |
18 |
> (I'm using portage 2.2_rc33) |
19 |
> |
20 |
> Many thanks for an explanation, |
21 |
> Helmut. |
22 |
|
23 |
It's from an inherited eclass: |
24 |
|
25 |
# grep inherit * |
26 |
gcc-4.3.3-r2.ebuild:inherit toolchain |
27 |
gcc-4.4.0.ebuild:inherit toolchain |
28 |
nazgul gcc # grep nptl /var/portage/eclass/toolchain.eclass |
29 |
IUSE="multislot nptl test" |
30 |
confgcc="${confgcc} --disable-__cxa_atexit --enable-target- |
31 |
optspace $(use_enable nptl tls)" |
32 |
|
33 |
-- |
34 |
alan dot mckinnon at gmail dot com |