Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #7090
| From | Jéremy Bobbio <lunar@debian.org> |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | Re: Sphinx 1.3 in Debian experimental |
| Date | 2015-07-07 13:20 +0200 |
| Message-ID | <pJz4S-4Y0-23@gated-at.bofh.it> (permalink) |
| References | (4 earlier) <pGLce-1mE-13@gated-at.bofh.it> <pGLFg-2aa-7@gated-at.bofh.it> <pGMhX-2Tw-3@gated-at.bofh.it> <pGMKZ-3Go-1@gated-at.bofh.it> <pGMUF-3RB-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
Dmitry Shachnev:
> Anyway, if you provide a suggestion for how to fix this on Sphinx side
> (not *so* hackish as parsing d/changelog), I will look at it.
Our current proposal is to implement support for the SOURCE_DATE_EPOCH
environment variable. See:
https://wiki.debian.org/ReproducibleBuilds/TimestampsProposal
It's already implemented in help2man, and we have patches ready for
txt2man, epydoc, and Doxygen.
> |today| is for Sphinx the same as __DATE__ is for a C compiler. You do not
> suggest to patch gcc to remove support for __DATE__, do you?
Actually, Dhole implemented a patch to add support for SOURCE_DATE_EPOCH
in GCC and asked upstream what they thought about it:
https://gcc.gnu.org/ml/gcc-patches/2015-06/msg02210.html
--
Lunar .''`.
lunar@debian.org : :Ⓐ : # apt-get install anarchism
`. `'`
`-
Back to linux.debian.maint.python | Previous | Next — Previous in thread | Find similar
Re: Sphinx 1.3 in Debian experimental Barry Warsaw <barry@python.org> - 2015-06-29 17:30 +0200 Re: Sphinx 1.3 in Debian experimental Jéremy Bobbio <lunar@debian.org> - 2015-07-07 13:20 +0200
csiph-web