public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Fabian Groffen <grobian@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] New package neomutt
Date: Thu, 10 Aug 2017 09:54:43 +0200	[thread overview]
Message-ID: <20170810075443.GR1321@gentoo.org> (raw)
In-Reply-To: <1502350830.1554.1.camel@gentoo.org>

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

On 10-08-2017 09:40:30 +0200, Michał Górny wrote:
> On czw, 2017-08-10 at 06:58 +0200, Nicolas Bock wrote:
> > On Mon, Jul 31, 2017 at 09:11:19AM +0200, Nicolas Bock wrote:
> > > Hi,
> > > 
> > > I would like to add neomutt to the tree. This new package is meant as 
> > > an alternative and not a replacement of the existing mutt package.
> > 
> > Thanks for all of the great suggestions and feedback!
> > 
> > This is round two. I have update the ebuild with all your 
> > suggestions. I have also added support for eselecting between mutt 
> > and neomutt. Before the eselect ebuild can land though, we need to 
> > rename the mutt binary so that the managed link can be called 
> > mutt.
> 
> What for? How many people are exactly in the dire need of having both
> installed simultaneously and switching between them? If you really can't
> learn to type the new command, add IUSE=symlink blocking original mutt
> and be done with it. Don't add more unowned files to /usr by another
> poorly written eselect module.

Be nice!  No need to be bitchy here (and in the rest of your review).
Nicolas is just trying.

Me, as maintainer of Mutt, thought it was a good idea, because it allows
people to easily have both installed at the same time, which in this
interesting time for both projects is not a weird thing to have.

If there is a policy/move to get rid of eselect, then sorry, I am not
aware of that.  I can live with a symlink USE-flag.  It doesn't seem
very elegant to me, but it would work for this scenario.


Thanks,
Fabian

-- 
Fabian Groffen
Gentoo on a different level

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2017-08-10  7:54 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 [this message]
2017-08-10  8:10       ` Michał Górny
2017-08-10  9:35         ` Nicolas Bock
2017-08-10 12:13           ` Marc Schiffbauer
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=20170810075443.GR1321@gentoo.org \
    --to=grobian@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