On Tue, Jul 16 2013, Neil Bothwick wrote:
> On Tue, 16 Jul 2013 09:49:42 -0400, gottl...@nyu.edu wrote:
>
>> gnome-control-center-3.6.3-r1.ebuild contains
>>
>> IUSE="+bluetooth +colord +cups +gnome-online-accounts +i18n
>> input_devices_wacom kerberos +networkmanager +socialweb systemd v4l"
>>
>> and
>>
>> COMMON_DEPEND="
>> ...
>> networkmanager? (
>> >=gnome-extra/nm-applet-0.9.1.90
>> >=net-misc/networkmanager-0.8.997 )
>>
>> I believe the first says that "if the networkmanager use flag is neither
>> set nor unset, treat it as set" and the second says
>> "if the use flag is set (or treated as set), require
>> net-misc/networkmanager".
>
> That's correct. The + just means it defaults to on, instead of the usual
> off default for USE flags.
>
>> I don't see how to have the flag "unset" since its default is "set".
>> For example, editing make.conf to add
>>
>> USE="-networkmanager"
>>
>> (I had no USE in make.conf previously) has no effect
>
> That should do exactly what you want, although you can do it
> in /etc/portage/package.use too (although that makes no sense in this
> case as the decision on which network manager to use must be global).
>
> Are you sure that you have spelled the USE flag correctly, that one has
> wasted significant chunks of my life before now 9and will probably do so
> again in the future).
I just did it again with cut and paste from above.
Now the end of make.conf is (from cut and paste)
FEATURES=" buildsyspkg"
USE="-networkmanager"
and I still get
newlap gottlieb # emerge --depclean networkmanager
Calculating dependencies... done!
net-misc/networkmanager-0.9.8.2 pulled in by:
gnome-base/gnome-control-center-3.6.3-r1 requires
>=net-misc/networkmanager-0.8.997
gnome-base/gnome-shell-3.6.3.1 requires
>=net-misc/networkmanager-0.8.999[introspection]
gnome-extra/nm-applet-0.9.6.4-r1 requires >=net-misc/networkmanager-0.9.6
net-libs/libsocialweb-0.25.21 requires net-misc/networkmanager
To be sure that make.conf was being consulted, I tried it with a
fictitious flag joeee, which "worked" and then with -joeee which "didn't
work". That is, putting -joeee in make.conf results in *neither* joeee
or -joeee in the USE printed by emerge --info
>> since networkmanager was not in USE before.
>
> This is irrelevant. No USE flags are in make.conf until you put them
> there.
My wording here was bad. I meant that networkmanager was not in the USE
shown by emerge --sync and apparently (to my surprise) specifying
-foo in make.conf only removes USEs from the emerge --sync listing
and does not insert -foo into the emerge --sync USE, assuming
that neither foo nor -foo was originally in emerge --sync USE.
I am sure I am doing something wrong since I agree that
USE="-networkmanager"
in make.conf should be just what is needed, but I don't think it is just
my misspelling networkmanager.
allan
