From: Joonas Niilola <juippis@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Inconsistent use of || preferences for www-client/elinks, links, lynx, w3m, and w3mmee
Date: Tue, 11 Feb 2020 15:47:29 +0200 [thread overview]
Message-ID: <e5579c14-72ad-de5d-7056-5c5856f03333@gentoo.org> (raw)
In-Reply-To: <CAD6zcDz5TQOkHn6K9Pmk3WTo4cCC40T=1=5Db9qdyC-pUnDmfQ@mail.gmail.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1131 bytes --]
On 2/11/20 12:32 PM, Francesco Riosa wrote:
>
>
> Il giorno lun 10 feb 2020 alle ore 08:20 Michał Górny
> <mgorny@gentoo.org <mailto:mgorny@gentoo.org>> ha scritto:
>
> On Sun, 2020-02-09 at 22:51 -0800, Zac Medico wrote:
> > In that case, I suppose we'll have to apply consistency
> manually? Can we
> > all agree on a global order of preference for the relevant packages?
>
> That would be my idea, yes. I'd suggest going for the 'lightest'
> package first. Would you be able to figure out some kind of measure
> on how heavy each of those packages is? I suppose we need to account
> for build time and dependencies.
>
> All of these packages are pretty old and not receiving commits in
> years, may I suggest that the order should be from the less prone to
> break to the most prone to break?
How do you determine this?
> I'll leave to maintainers decide on how to assign a vote on resilience,
Ah. So no.
Whats wrong with simply sorting by alphabetic order? Elinks seems a fine
default for those who don't care enough to change it.
-- juippis
[-- Attachment #1.1.2: Type: text/html, Size: 3119 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 642 bytes --]
prev parent reply other threads:[~2020-02-11 13:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-10 6:30 [gentoo-dev] Inconsistent use of || preferences for www-client/elinks, links, lynx, w3m, and w3mmee Zac Medico
2020-02-10 6:44 ` Michał Górny
2020-02-10 6:51 ` Zac Medico
2020-02-10 7:19 ` Michał Górny
2020-02-11 10:32 ` Francesco Riosa
2020-02-11 13:47 ` Joonas Niilola [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e5579c14-72ad-de5d-7056-5c5856f03333@gentoo.org \
--to=juippis@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox