On Tue, Jun 30, 2015 at 5:05 AM, Dmitry Shachnev <mity...@debian.org> wrote:
> Hi,
>
> On Tue, 30 Jun 2015 10:47:34 +0200, Piotr Ożarowski wrote:
>> [Dmitry Shachnev, 2015-06-30]
>>> Looking at the source of Sphinx' distutils/setuptools command [1],
>>> I see that pybuild can already help here by including something like this
>>> in its generated setup.cfg:
>>>
>>>   [build_sphinx]
>>>   today = {date from debian/changelog} [2]
>>>
>>> Piotr, do you think you can add this?
>>
>> sure
>
> Thinking again about this, it will help only for packages where build_sphinx
> is envoked during setup.py build. For those packages where setup.py 
> build_sphinx
> is called explicitly from debian/rules, pybuild can't do anything.
>
> But on the other hand, for the latter group of packages setting an env 
> variable
> in pybuild won't help as well. So we still don't have any solution that will
> help making *majority* of packages reproducible without changing each of them.

yeah, please dont bind the solution to pybuild, or at least give a way
to people not using it to be able to address the issue.

Cheers,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi


--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/CAB4XWXw704DcLQUYiMoKeVmujM=fgcjrmt9yn___ccgkacr...@mail.gmail.com

Reply via email to