supported-network-client review

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

supported-network-client review

Julian Andres Klode-2
Hi all,

tl;dr drop jigit, could consider neomutt instead of mutt

I was looking at where irssi came from, and found supported-network-client. Saw
jigit in it, decided to give it a short review.

(tagged OK/RM/?? for keep/remove/maybe)

$ cat supported-network-client  | sed 's#^#> #'
> = Clients =
>
>  * irssi

OK Having a text IRC client makes sense I guess, though it would not
be my choice :)

>  * avahi-utils

OK Useful to debug avahi issues I guess.

>
> = Download =
>
>  * jigit                  # specialised Debian/Ubuntu CD image download

RM I'm not sure there's much of a use anymore, so I'd say let's drop it.
 
> = Mail =
>
>  * mutt

?? We _could_ switch to neomutt, which is more advanced, and was packaged
as mutt for some time. The code base started out the same, but got quite
refactoring done recently, and there is progress in adding multi-account
support. It would pull in (lib)notmuch, though.

>  * lbdb

OK Never used that, but sounds interesting.

--
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer                              i speak de, en

--
ubuntu-devel mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Reply | Threaded
Open this post in threaded view
|

Re: supported-network-client review

Steve Langasek-6
Hi Julian,

On Wed, Jan 16, 2019 at 03:28:38PM +0100, Julian Andres Klode wrote:

> > = Download =

> >  * jigit                  # specialised Debian/Ubuntu CD image download

> RM I'm not sure there's much of a use anymore, so I'd say let's drop it.

Seems appropriate to me, can you raise an MP?

> > = Mail =

> >  * mutt

> ?? We _could_ switch to neomutt, which is more advanced, and was packaged
> as mutt for some time. The code base started out the same, but got quite
> refactoring done recently, and there is progress in adding multi-account
> support. It would pull in (lib)notmuch, though.

Have we lost anything with mainstream mutt in 18.10 vs. what we had with
neomutt in 17.10?

Given that we were previously using neomutt as mutt (based on the Debian
maintainer's decisions at the time), if we were going to switch back to
neomutt, should we rather do so by shipping neomutt as mutt again?

--
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
Ubuntu Developer                                   https://www.debian.org/
[hidden email]                                     [hidden email]

--
ubuntu-devel mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel

signature.asc (849 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: supported-network-client review

Julian Andres Klode
(switching to the email I'm actually subscribed with)

On Sat, Jan 19, 2019 at 10:31:31PM +0200, Steve Langasek wrote:

> Hi Julian,
>
> On Wed, Jan 16, 2019 at 03:28:38PM +0100, Julian Andres Klode wrote:
>
> > > = Download =
>
> > >  * jigit                  # specialised Debian/Ubuntu CD image download
>
> > RM I'm not sure there's much of a use anymore, so I'd say let's drop it.
>
> Seems appropriate to me, can you raise an MP?
https://code.launchpad.net/~juliank/ubuntu-seeds/+git/platform/+merge/362002

>
> > > = Mail =
>
> > >  * mutt
>
> > ?? We _could_ switch to neomutt, which is more advanced, and was packaged
> > as mutt for some time. The code base started out the same, but got quite
> > refactoring done recently, and there is progress in adding multi-account
> > support. It would pull in (lib)notmuch, though.
>
> Have we lost anything with mainstream mutt in 18.10 vs. what we had with
> neomutt in 17.10?
The major features I guess are

* NNTP support
* notmuch support

I find the first quite useful with gmane.

https://neomutt.org/feature.html lists quite a lot more features.

>
> Given that we were previously using neomutt as mutt (based on the Debian
> maintainer's decisions at the time), if we were going to switch back to
> neomutt, should we rather do so by shipping neomutt as mutt again?

I feel like that would end up in a cdrecord-like situation with mutt's
upstream.

--
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer                              i speak de, en

--
ubuntu-devel mailing list
[hidden email]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel

signature.asc (849 bytes) Download Attachment