FS#59715 - [mutt] gpgring and gpgewrap shoud be installed under /usr/lib/mutt/
Attached to Project:
Arch Linux
Opened by Bruno Pagani (ArchangeGabriel) - Sunday, 19 August 2018, 09:31 GMT
Last edited by Gaetan Bisson (vesath) - Wednesday, 05 September 2018, 02:11 GMT
Opened by Bruno Pagani (ArchangeGabriel) - Sunday, 19 August 2018, 09:31 GMT
Last edited by Gaetan Bisson (vesath) - Wednesday, 05 September 2018, 02:11 GMT
|
Details
Currently, those binaries are under `/usr/bin`, which
conflicts with other packages like signing-party which is
waiting amongst other things for this to be solved before
entering [community].
Debian does this for mutt, neomutt does this too, and I’m not exactly sure but I would say it’s just a missing `--libexecdir=/usr/lib` (haven’t tried though). |
This task depends upon
Closed by Gaetan Bisson (vesath)
Wednesday, 05 September 2018, 02:11 GMT
Reason for closing: Implemented
Additional comments about closing: mutt-1.10.1-2 in [extra]
Wednesday, 05 September 2018, 02:11 GMT
Reason for closing: Implemented
Additional comments about closing: mutt-1.10.1-2 in [extra]
bin_PROGRAMS = mutt$(EXEEXT) $(DOTLOCK_TARGET) $(PGPAUX_TARGET)
In other words, the PGP aux stuff (defined by configure to be pgpring and pgpewrap) is installed as regular binaries just like mutt.
If neomutt has a patch for this, perhaps you could suggested it be incorporated in upstream mutt?
https://salsa.debian.org/mutt-team/mutt/blob/master/debian/patches/misc/gpg.rc-paths.patch
And they just move the two binaries manually in their packaging script. I don’t know how neomutt changed that (and I don’t have time currently to dig in their code), but in any case I’ve submitted https://gitlab.com/muttmua/mutt/issues/71.
Can that commit be backported to our current version?