Gentoo Archives: gentoo-dev

From: "Michał Górny" <mgorny@g.o>
To: gentoo-dev@l.g.o
Cc: dotnet@g.o, Fabian Groffen <grobian@g.o>, nicolasbock@g.o, swegener@g.o, monsieurp@g.o, zlogene@g.o, x11@g.o
Subject: Re: [gentoo-dev] Inconsistent use of || preferences for www-client/elinks, links, lynx, w3m, and w3mmee
Date: Mon, 10 Feb 2020 06:45:09
Message-Id: d31566fc6fe7563200d65c66a8514ff098b784c1.camel@gentoo.org
In Reply to: [gentoo-dev] Inconsistent use of || preferences for www-client/elinks, links, lynx, w3m, and w3mmee by Zac Medico
1 On Sun, 2020-02-09 at 22:30 -0800, Zac Medico wrote:
2 > Hi all (especially package owners in CC),
3 >
4 > In various packages we have inconsistent use of || preferences for
5 > www-client/elinks, links, lynx, w3m, and w3mmee. This means that the
6 > default preference depends on the combination of packages that one has
7 > installed and the order that one has installed them, leading to
8 > unpredictable results.
9 >
10 > Here is a list of relevant packages and their dependencies:
11 >
12 > app-text/docbook-sgml-utils: || ( www-client/lynx www-client/links
13 > www-client/elinks virtual/w3m )
14 > app-text/sgmltools-lite: || ( www-client/w3m www-client/lynx )
15 > app-text/xmlto: || ( virtual/w3m www-client/lynx www-client/elinks )
16 > dev-lang/mono: || ( www-client/links www-client/lynx )
17 > mail-client/mutt: || ( www-client/lynx www-client/w3m www-client/elinks )
18 > mail-client/neomutt: || ( www-client/lynx www-client/w3m www-client/elinks )
19 > net-irc/irssi: || ( www-client/lynx www-client/elinks )
20 > sys-fs/gt5: || ( www-client/links www-client/elinks www-client/lynx )
21 > x11-base/xorg-server: || ( www-client/links www-client/lynx www-client/w3m )
22 >
23 > How about if we create some more virtuals to cover all of the relevant
24 > cases?
25
26 I don't think that's a valid case for a virtual since those tools do not
27 provide a consistent API for other packages. It just happens that some
28 packages explicitly support multiple choices, and this is exactly what
29 || indicates.
30
31 The virtuals would really be arbitrary here. Developers would
32 repeatedly fail to use them because they wouldn't naturally expect
33 the virtual to exist.
34
35 >
36 > We've already got virtual/w3m to cover this particular case:
37 >
38 > || ( www-client/w3m www-client/w3mmee )
39 >
40 > We might want to use nested virtuals, in the same way that virtual/jdk
41 > nests under virtual/jre.
42
43 --
44 Best regards,
45 Michał Górny

Attachments

File name MIME type
signature.asc application/pgp-signature

Replies