[arch-general] Mutt Compile-time Configuration

older
Re: [arch-general] arch-general...

Dutch Ingraham

20 Aug 2016 20 Aug '16

1:09 a.m.

Hello all: Mutt 1.7.0 was just released.[1] One new feature is the sidebar, which up to now required a patched version of mutt from the AUR. However, it is a compile-time option and it appears as though the Arch packager has decided to not enable it (my muttrc will throw an error if I try and configure the sidebar.) Can someone more familiar than myself explain why a packager would decide to do this? In other words, what are the general considerations for including certain options at compile-time? (In this particular case, the sidebar would not be turned on until configured in the muttrc, so compiling the option into the package would not affect those who do not want it.) Thanks for your replies. [1]https://marc.info/?l=mutt-users&m=147154326009383

Show replies by date

Bruno Pagani

20 Aug 20 Aug

1:39 a.m.

Le 20 août 2016 01:09:06 GMT+02:00, Dutch Ingraham a écrit :

...

Hello all:

Mutt 1.7.0 was just released.[1] One new feature is the sidebar, which up to now required a patched version of mutt from the AUR. However, it is a compile-time option and it appears as though the Arch packager has decided to not enable it (my muttrc will throw an error if I try and configure the sidebar.)

I think that the packager just didn’t see this addition and only bounced the pkgver. There is an open ticket about this: https://bugs.archlinux.org/task/50445.

...

Can someone more familiar than myself explain why a packager would decide to do this? In other words, what are the general considerations for including certain options at compile-time? (In this particular case, the sidebar would not be turned on until configured in the muttrc, so compiling the option into the package would not affect those who do not want it.)

It depends on a lot of things I think. Overhead of the option (in terms of dependencies especially, but also size, etc.), likelyhood of being use by a majority of users, whether it’s upstream default/recommandation… But in this particular case, like I said, I think that the packager just didn’t see that there was this new option, and since it’s not on by default… So just upvote the ticket if it’s not yours, and wait for the packager to react there. ;) Bruno

Thibaut Marty

2:09 a.m.

On Sat, Aug 20, 2016 at 01:39:28AM +0200, Bruno Pagani wrote:

...

I think that the packager just didn’t see this addition and only bounced the pkgver. There is an open ticket about this: https://bugs.archlinux.org/task/50445.

This would be surprising, as the new compile-time option was explicitly given in the release announce mail. Does that mean the packager did not subscribe to the very low-traffic mutt announce list or did not read it before updating the package? However, the UPDATING file does not mention the new option. -- Thibaut

Jason Ryan

2:14 a.m.

On 20/08/16 at 02:09am, Thibaut Marty wrote:

...

On Sat, Aug 20, 2016 at 01:39:28AM +0200, Bruno Pagani wrote:

...
I think that the packager just didn’t see this addition and only bounced the pkgver. There is an open ticket about this: https://bugs.archlinux.org/task/50445.

This would be surprising, as the new compile-time option was explicitly given in the release announce mail. Does that mean the packager did not subscribe to the very low-traffic mutt announce list or did not read it before updating the package? However, the UPDATING file does not mention the new option.

Or maybe they read it and just figured that anyone who wanted it would build it themselves… In any event, vesath has already pushed a version with it included. /J -- http://jasonwryan.com/ GPG: 7817 E3FF 578E EEE1 9F64 D40C 445E 52EA B1BD 4E40

Dutch Ingraham

2:20 a.m.

On Sat, Aug 20, 2016 at 02:09:47AM +0200, Thibaut Marty wrote:

...

On Sat, Aug 20, 2016 at 01:39:28AM +0200, Bruno Pagani wrote:

...
I think that the packager just didn’t see this addition and only bounced the pkgver. There is an open ticket about this: https://bugs.archlinux.org/task/50445.

Thanks, Bruno - you're probably right.

...

This would be surprising, as the new compile-time option was explicitly given in the release announce mail. Does that mean the packager did not subscribe to the very low-traffic mutt announce list or did not read it before updating the package? However, the UPDATING file does not mention the new option.

Well, the maintainer just enabled it in an updated package, so all's moot at this point. In fact, I was in the middle of adding a comment to the feature request regarding updating the wiki when the ticket was closed and blew away my comment. Hopefully someone will get to it. Thanks both for your replies!

Gaetan Bisson

2:30 a.m.

[2016-08-20 01:39:28 +0200] Bruno Pagani:

...

Le 20 août 2016 01:09:06 GMT+02:00, Dutch Ingraham a écrit :

...
Hello all:

Mutt 1.7.0 was just released.[1] One new feature is the sidebar, which up to now required a patched version of mutt from the AUR. However, it is a compile-time option and it appears as though the Arch packager has decided to not enable it (my muttrc will throw an error if I try and configure the sidebar.)

I think that the packager just didn’t see this addition and only bounced the pkgver.

Almost: I saw the addition but assumed it'd be enabled by default. What's curious to me is that upstream chose not to enable a useful no-overhead option by default... Anyhow, I hope you'll be pleased with mutt-1.7.0-2. -- Gaetan

Jude DaShiell

6:52 a.m.

talkingarch users who haven't got g.u.i. running may have problems with that sidebar due to graphical character output from that feature messing up their screen readers. There could be other or additional reasons I know nothing about yet too. On Fri, 19 Aug 2016, Dutch Ingraham wrote:

...

Date: Fri, 19 Aug 2016 19:09:06 From: Dutch Ingraham Reply-To: General Discussion about Arch Linux To: arch-general@archlinux.org Subject: [arch-general] Mutt Compile-time Configuration

Hello all:

Mutt 1.7.0 was just released.[1] One new feature is the sidebar, which up to now required a patched version of mutt from the AUR. However, it is a compile-time option and it appears as though the Arch packager has decided to not enable it (my muttrc will throw an error if I try and configure the sidebar.)

Can someone more familiar than myself explain why a packager would decide to do this? In other words, what are the general considerations for including certain options at compile-time? (In this particular case, the sidebar would not be turned on until configured in the muttrc, so compiling the option into the package would not affect those who do not want it.)

Thanks for your replies.

[1]https://marc.info/?l=mutt-users&m=147154326009383

Hunter Connelly

5:12 p.m.

On Sat, Aug 20, 2016 at 12:52:36AM -0400, Jude DaShiell wrote:

...

talkingarch users who haven't got g.u.i. running may have problems with that sidebar due to graphical character output from that feature messing up their screen readers. There could be other or additional reasons I know nothing about yet too.

As OP said, the sidebar would not be turned on until it is configured in the muttrc. Compiling the sidebar in would not affect current users of the non-sidebar mutt package.

2803

Age (days ago)

2804

Last active (days ago)

List overview

Download

7 comments

7 participants

participants (7)

Bruno Pagani
Dutch Ingraham
Gaetan Bisson
Hunter Connelly
Jason Ryan
Jude DaShiell
Thibaut Marty