public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Marc Schiffbauer <mschiff@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] New package neomutt
Date: Thu, 10 Aug 2017 14:13:29 +0200	[thread overview]
Message-ID: <20170810121329.GG9622@schiffbauer.net> (raw)
In-Reply-To: <20170810093545.qhgn7iuuxn6l5dfk@rubberducky.suse.de>

[-- Attachment #1: Type: text/plain, Size: 910 bytes --]

* Nicolas Bock schrieb am 10.08.17 um 11:35 Uhr:
> It does of course. What's appropriate here depends on whether we 
> think somebody might want to have both mutt and neomutt installed 
> at the same time. If we don't allow this use case, we don't have 
> to worry about eselect and the neomutt binary will be called 
> 'mutt' (as it is called by upstream already). If we do allow this 
> use case, being able to eselect makes sense because then the 
> binary is still always called 'mutt'.

Why not just have mutt and/or neomutt for both packages? Whoever only 
wants neomutt and run it with 'mutt' can "alias mutt=neomutt" and be 
done.

Having en eselect module here is not really KISS and looks a bit like 
bloat to me which make things more complicated than they have to be.

Just my 2¢

-- 
0xCA3E7BF67F979BE5 - F7FB 78F7 7CC3 79F6 DF07
                     6E9E CA3E 7BF6 7F97 9BE5

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2017-08-10 12:13 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-31  7:11 [gentoo-dev] New package neomutt Nicolas Bock
2017-07-31  7:23 ` Nicolas Bock
2017-07-31  8:34   ` Patrice Clement
2017-08-10  4:37     ` Nicolas Bock
2017-07-31 12:15   ` Floyd Anderson
2017-08-10  4:34     ` Nicolas Bock
2017-07-31  7:44 ` Michał Górny
2017-07-31  7:59   ` Nicolas Bock
2017-07-31  9:55 ` Matthew Thode
2017-07-31 10:52   ` Fabian Groffen
2017-08-05 20:13     ` Matthew Marchese
2017-08-10  4:58 ` Nicolas Bock
2017-08-10  7:40   ` Michał Górny
2017-08-10  7:54     ` Fabian Groffen
2017-08-10  8:10       ` Michał Górny
2017-08-10  9:35         ` Nicolas Bock
2017-08-10 12:13           ` Marc Schiffbauer [this message]
2017-08-10 12:16             ` Fabian Groffen
2017-08-10 14:09               ` Michał Górny
2017-08-10 14:32                 ` Fabian Groffen
2017-08-10 13:59           ` Michał Górny
2017-08-17  5:07         ` Daniel Campbell
2017-08-17  7:48           ` Michał Górny
2017-08-18  1:01             ` Daniel Campbell
2017-09-18 12:02     ` Nicolas Bock
2017-08-10 18:25   ` William Hubbs
2017-09-18 12:08 ` Nicolas Bock
2017-10-03 12:36   ` Nicolas Bock
2017-10-03 20:09     ` Marty E. Plummer
2017-10-03 20:33       ` Nicolas Bock

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=20170810121329.GG9622@schiffbauer.net \
    --to=mschiff@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