Gentoo Archives: gentoo-portage-dev

From: Zac Medico <zmedico@g.o>
To: gentoo-portage-dev@l.g.o
Subject: Re: [gentoo-portage-dev] Re: [PATCH 2/2 v2] depgraph: soname dependency resolution (282639)
Date: Sat, 14 Feb 2015 06:05:54
Message-Id: 54DEE5BC.9040200@gentoo.org
In Reply to: [gentoo-portage-dev] Re: [PATCH 2/2 v2] depgraph: soname dependency resolution (282639) by Duncan <1i5t5.duncan@cox.net>
1 On 02/13/2015 07:03 PM, Duncan wrote:
2 > Zac Medico posted on Fri, 13 Feb 2015 10:35:09 -0800 as excerpted:
3 >
4 >> Soname dependency resolution is enabled when --ignore-soname-deps=n is
5 >> specified, and [...]
6 >
7 > Can that option possibly be renamed?
8 >
9 > "Ignore" is functionally a negative, as in "don't consider". As a
10 > result, --ignore-sonames-deps=n is a double-negative that actually
11 > enables something, and it becomes rather difficult to reason about what
12 > you're actually telling portage to do.
13 >
14 > Unfortunately, I'm confused enough myself that I don't have any
15 > suggestions for any better option name. =:^(
16
17 Well, the "ignore" prefix is there to express that something is being
18 ignored. In a couple of years, we'll be able to enable soname dependency
19 resolution by default, and the --ignore-soname-deps=y option will be
20 there for people to use in rare cases where it might be helpful (like on
21 outdated systems where soname metadata isn't available for installed
22 packages).
23
24 > In case there's any doubt about how much trouble English speakers often
25 > have with multiple negation, I follow a linguists blog called LanguageLog,
26 > that regularly features examples of "misnegation", in which all sorts of
27 > people have ended up saying the opposite of what they obviously intended
28 > because of an incorrect number of negations. People really do have
29 > trouble sorting it out, and some of the examples are actually quite
30 > humorous.
31 >
32 > Here's a google on "misnegation". At least from here, the top three hits
33 > are Language log, with #3 being a big list of posts on the topic.
34 >
35 > https://www.google.com/search?q=misnegation&ie=UTF-8
36 >
37 > And here's one of the more amusing ones, a billboard at a(n apparently
38 > UK) petrol/gas station:
39 >
40 > http://languagelog.ldc.upenn.edu/nll/?p=14927
41 >
42 > (FWIW, I recently emailed the author of a popular FLOSS community
43 > standards blog about a misnegation as well. He fixed it, and sent me a
44 > nice reply/thanks.)
45 >
46 >
47 > So, umm... Let's come up with some other option name here, one that
48 > doesn't invoke multiple negation to turn ON a function, and thus hurt to
49 > think about, if at all possible. =:^/
50 >
51 > Tho arguably with the double negation turning something ON, at least
52 > we're not misnegating here. It's confusing and hard to think about, but
53 > AFAICT, logically correct. =:^) Of course that doesn't mean people can
54 > actually /use/ it correctly, thus the problem. =:^\
55
56 I see what you mean, but I still think having "ignore" in then name is a
57 good way to express the meaning. It's similar to the --nodeps option,
58 which also begins with a negative.
59 --
60 Thanks,
61 Zac