who finds support for rst2man in the notmuch build process useful?
Recently in discussion of at id:1420300167-5060-1-git-send-email-david at tethera.net it was proposed we could just eliminate support for non-sphinx based methods of building the docs. This would require sphinx >= 1.0 and python-docutils 0.6 to build the docs. The win for us would be to eliminate some custom python scripting in the build process to fake some small part of sphinx functionality; it would also allow us to use more features of sphinx in the .rst source. Version 1.0 of sphinx is from 2010, and is present e.g. in Debian stable. We are having a bit of dependency creep here. One option would be to generate seperate tarballs of the pre-formatted man pages during the release process; this _should_ be a matter of running "tar" on the build tree. -- next part -- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 647 bytes Desc: not available URL: <http://notmuchmail.org/pipermail/notmuch/attachments/20150104/4556deb8/attachment.pgp>
[PATCH 1/2] configure: add check for python interepreter name
David Bremner writes: > Currently we hardcode "python" in several places. This makes things > hard for people who have only commands called python3 and/or > python2. We also add the name to sh.config to eventually replace the > current workaround in the test suite. Pushed, with Tomi's suggested addition of at least removing the hard coding of python in the configure script itself.
[PATCH] build: eliminate use of python execfile command
David Bremner writes: > As discussed in > id:8cc9dd580ad672527e12f43706f9803b2c8e99d8.1405220724.git.wking at > tremily.us, > execfile is unavailable in python3. Pushed, with commit message reformatted. d
intent to remove notmuch-deliver from contrib
Since we've deprecated notmuch-deliver, and don't plan on shipping it with the next release of notmuch, it makes sense to delete it from git master. Of course it will still exist in old versions if it needs to be retrieved for some reason. Please let me know within the next week or so if there is some compelling reason why I shouldn't remove it. d -- next part -- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 647 bytes Desc: not available URL: <http://notmuchmail.org/pipermail/notmuch/attachments/20150104/bc11021e/attachment.pgp>
intent to remove notmuch-deliver from contrib
Since we've deprecated notmuch-deliver, and don't plan on shipping it with the next release of notmuch, it makes sense to delete it from git master. Of course it will still exist in old versions if it needs to be retrieved for some reason. Please let me know within the next week or so if there is some compelling reason why I shouldn't remove it. d signature.asc Description: PGP signature ___ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch
Re: [PATCH] build: eliminate use of python execfile command
David Bremner da...@tethera.net writes: As discussed in id:8cc9dd580ad672527e12f43706f9803b2c8e99d8.1405220724.git.wk...@tremily.us, execfile is unavailable in python3. Pushed, with commit message reformatted. d ___ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch
Re: [PATCH 1/2] configure: add check for python interepreter name
David Bremner da...@tethera.net writes: Currently we hardcode python in several places. This makes things hard for people who have only commands called python3 and/or python2. We also add the name to sh.config to eventually replace the current workaround in the test suite. Pushed, with Tomi's suggested addition of at least removing the hard coding of python in the configure script itself. ___ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch
who finds support for rst2man in the notmuch build process useful?
Recently in discussion of at id:1420300167-5060-1-git-send-email-da...@tethera.net it was proposed we could just eliminate support for non-sphinx based methods of building the docs. This would require sphinx = 1.0 and python-docutils 0.6 to build the docs. The win for us would be to eliminate some custom python scripting in the build process to fake some small part of sphinx functionality; it would also allow us to use more features of sphinx in the .rst source. Version 1.0 of sphinx is from 2010, and is present e.g. in Debian stable. We are having a bit of dependency creep here. One option would be to generate seperate tarballs of the pre-formatted man pages during the release process; this _should_ be a matter of running tar on the build tree. signature.asc Description: PGP signature ___ notmuch mailing list notmuch@notmuchmail.org http://notmuchmail.org/mailman/listinfo/notmuch
