FS#56038 - [neomutt] should provide mutt

Attached to Project: Community Packages
Opened by Moabit (Moabit) - Wednesday, 18 October 2017, 21:25 GMT
Last edited by Alad Wenter (Alad) - Thursday, 19 October 2017, 08:31 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Alad Wenter (Alad)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
neomutt has just moved from AUR to community. However, the PKGBUILD has changed. The old package provided mutt, but the new version does not. Other packages depend on mutt (including neomutt), such as the following two.

https://aur.archlinux.org/packages/mutt-solarized-git/
https://aur.archlinux.org/packages/mutt-vid/

Additional info:
* package version(s): 20171013-2

Steps to reproduce:
Attempt to upgrade. Pacman refuses because of broken dependencies.

There are also a few dependencies of the AUR package that didn't make it to the community version:
openssl gdbm libsasl gnupg gpgme libidn krb5

I'm not sure if these were required, but I would have thought at the very least they could be moved to optdepends?
This task depends upon

Closed by  Alad Wenter (Alad)
Thursday, 19 October 2017, 08:31 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Create a "neomutt-symlinks" package or similar to support your old AUR packages. See the comments.
Comment by Eli Schwartz (eschwartz) - Thursday, 19 October 2017, 04:19 GMT
The dependencies will all be present on a base install as they are dependencies of e.g. systemd, pacman, coreutils etc. Some of them are low-level enough that they directly depend on each other.

It could be argued that if in the future pacman stops depending on gpgme/gnupg and openssl stops being a core component of most things ever including most of the base group, that this package will need to be updated to hardcode those dependencies. OTOH you could just as easily call that bloat.

EDIT: as Alad said, notmuch-runtime eventually drags in all these packages, which is essentially what I meant. Eventually things usually depend on these if you inspect their deptree.

`pactree -s neomutt` shows:

neomutt
├─notmuch-runtime
│ ├─xapian-core
│ │ └─util-linux
│ │ ├─pam
│ │ │ ├─libtirpc
│ │ │ │ └─krb5
│ │ │ │ ├─libldap
│ │ │ │ │ ├─libsasl
│ │ │ │ │ │ └─openssl
│ │ │ │ │ │ └─perl
│ │ │ │ ├─gdbm
│ ├─gmime
│ │ ├─gpgme
│ │ │ └─gnupg
│ │ │ ├─gnutls
│ │ │ │ ├─libidn
Comment by Moabit (Moabit) - Thursday, 19 October 2017, 04:26 GMT
Okay, that makes sense. Thank you for the clear answer.
Comment by Alad Wenter (Alad) - Thursday, 19 October 2017, 08:23 GMT
notmuch-runtime provides all the required dependencies, no implicit depends on base are involved. You can run namcap on the package from the old PKGBUILD to check for yourself.

As to provides on mutt, I have no interest in adding it. The file paths have changed to replace "mutt" with "neomutt", and otherwise there's no assurance that neomutt will remain a drop-in replacement: the goal of the project has changed from a patchset to an actual fork (same reason why it was added to the repos).

I would suggest to instead create a variant of neovim-symlinks (https://aur.archlinux.org/packages/neovim-symlinks/), e.g. "neomutt-symlinks", and submit it to AUR or keep it for your personal use.

Loading...