| 1 |
On Tue, Jul 16 2013, Neil Bothwick wrote: |
| 2 |
|
| 3 |
> On Tue, 16 Jul 2013 09:49:42 -0400, gottlieb@×××.edu wrote: |
| 4 |
> |
| 5 |
>> gnome-control-center-3.6.3-r1.ebuild contains |
| 6 |
>> |
| 7 |
>> IUSE="+bluetooth +colord +cups +gnome-online-accounts +i18n |
| 8 |
>> input_devices_wacom kerberos +networkmanager +socialweb systemd v4l" |
| 9 |
>> |
| 10 |
>> and |
| 11 |
>> |
| 12 |
>> COMMON_DEPEND=" |
| 13 |
>> ... |
| 14 |
>> networkmanager? ( |
| 15 |
>> >=gnome-extra/nm-applet-0.9.1.90 |
| 16 |
>> >=net-misc/networkmanager-0.8.997 ) |
| 17 |
>> |
| 18 |
>> I believe the first says that "if the networkmanager use flag is neither |
| 19 |
>> set nor unset, treat it as set" and the second says |
| 20 |
>> "if the use flag is set (or treated as set), require |
| 21 |
>> net-misc/networkmanager". |
| 22 |
> |
| 23 |
> That's correct. The + just means it defaults to on, instead of the usual |
| 24 |
> off default for USE flags. |
| 25 |
> |
| 26 |
>> I don't see how to have the flag "unset" since its default is "set". |
| 27 |
>> For example, editing make.conf to add |
| 28 |
>> |
| 29 |
>> USE="-networkmanager" |
| 30 |
>> |
| 31 |
>> (I had no USE in make.conf previously) has no effect |
| 32 |
> |
| 33 |
> That should do exactly what you want, although you can do it |
| 34 |
> in /etc/portage/package.use too (although that makes no sense in this |
| 35 |
> case as the decision on which network manager to use must be global). |
| 36 |
> |
| 37 |
> Are you sure that you have spelled the USE flag correctly, that one has |
| 38 |
> wasted significant chunks of my life before now 9and will probably do so |
| 39 |
> again in the future). |
| 40 |
|
| 41 |
I just did it again with cut and paste from above. |
| 42 |
Now the end of make.conf is (from cut and paste) |
| 43 |
|
| 44 |
FEATURES=" buildsyspkg" |
| 45 |
|
| 46 |
USE="-networkmanager" |
| 47 |
|
| 48 |
and I still get |
| 49 |
|
| 50 |
newlap gottlieb # emerge --depclean networkmanager |
| 51 |
|
| 52 |
Calculating dependencies... done! |
| 53 |
net-misc/networkmanager-0.9.8.2 pulled in by: |
| 54 |
gnome-base/gnome-control-center-3.6.3-r1 requires |
| 55 |
>=net-misc/networkmanager-0.8.997 |
| 56 |
gnome-base/gnome-shell-3.6.3.1 requires |
| 57 |
>=net-misc/networkmanager-0.8.999[introspection] |
| 58 |
gnome-extra/nm-applet-0.9.6.4-r1 requires >=net-misc/networkmanager-0.9.6 |
| 59 |
net-libs/libsocialweb-0.25.21 requires net-misc/networkmanager |
| 60 |
|
| 61 |
To be sure that make.conf was being consulted, I tried it with a |
| 62 |
fictitious flag joeee, which "worked" and then with -joeee which "didn't |
| 63 |
work". That is, putting -joeee in make.conf results in *neither* joeee |
| 64 |
or -joeee in the USE printed by emerge --info |
| 65 |
|
| 66 |
>> since networkmanager was not in USE before. |
| 67 |
> |
| 68 |
> This is irrelevant. No USE flags are in make.conf until you put them |
| 69 |
> there. |
| 70 |
|
| 71 |
My wording here was bad. I meant that networkmanager was not in the USE |
| 72 |
shown by emerge --sync and apparently (to my surprise) specifying |
| 73 |
-foo in make.conf only removes USEs from the emerge --sync listing |
| 74 |
and does not insert -foo into the emerge --sync USE, assuming |
| 75 |
that neither foo nor -foo was originally in emerge --sync USE. |
| 76 |
|
| 77 |
I am sure I am doing something wrong since I agree that |
| 78 |
USE="-networkmanager" |
| 79 |
in make.conf should be just what is needed, but I don't think it is just |
| 80 |
my misspelling networkmanager. |
| 81 |
|
| 82 |
allan |
Archives