https://bugzilla.redhat.com/show_bug.cgi?id=2086484



--- Comment #16 from Richard Russon <[email protected]> ---
Spec URL:
https://download.copr.fedorainfracloud.org/results/flatcap/neomutt-test/fedora-36-x86_64/04570893-neomutt/neomutt.spec
SRPM URL:
https://download.copr.fedorainfracloud.org/results/flatcap/neomutt-test/fedora-36-x86_64/04570893-neomutt/neomutt-20220628-1.fc36.src.rpm

Note: This has been built against a development version of NeoMutt, which has
some bugs.

> We do still need to put the finishing touches on the documentation/license 
> handling.

>  %{make_install}
> +rm %{buildroot}%{_pkgdocdir}/INSTALL.md %{buildroot}%{_pkgdocdir}/LICENSE.md

done

> +%{_pkgdocdir}

done.  much tidier :-)

> one more tweak to resolve an "ambiguous python shebang" error
> +sed -e '1 s/python/python3/' -i %{buildroot}%{_pkgdocdir}/keybase/keybase.py

We decided instead to drop the keybase script -- unmaintained, unused

----------------------

Other changes:

The contrib files (all the non-docs) have been moved to /usr/share/neomutt
I've added: `%{_datadir}` to the `%files` section to cover them.

I've added a patch: neomutt-fedora_colors.patch
(Each distro seems to have its own custom colours)
The spec *used* to grep the config out of another file (now deceased).

License: as keybase.py has gone, so has one of the license types (Unlicense).

Thanks!


-- 
You are receiving this mail because:
You are always notified about changes to this product and component
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2086484
_______________________________________________
package-review mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Reply via email to