Niko Tyni writes:
> A downside of this is that POD_MAN_DATE will affect all the manual pages
> generated by Pod::Man and remove the potentially useful indications of
> their recency. I can't really see how to avoid that, but possibly we
> should set POD_MAN_DATE to something that isn't really a t
Уважаеми
Дами
и Господа,
TBM
CONSULTING има
удоволствието да Ви покани да участвате в
предстоящите
семинари на
тема:
ПРАКТИЧЕСКИ АСПЕКТИ НА
РАЗРАБОТВАНЕТО И ИЗПЪЛНЕНИЕТО НА
ЕВРОПЕЙСКИ ПРОЕКТИ, ФИНАНСИРАНИ ПО
ПРОГРАМИ НА ЕС ПРЕЗ НОВИЯ ПРОГРАМЕН
ПЕРИОД 2014 - 2020. ОДИТ НА ПР
On Wed, Mar 11, 2015 at 10:01:07AM +, Chris Lamb wrote:
> While working on the "reproducible builds" effort [1], we have noticed
> that Pod::Man generates output that varies depending on the current
> timezone.
>
> The attached patch fixes this by using GMT (~UTC) dates instead
Thanks. Unlik
Hi,
Holger Levsen wrote:
> On Dienstag, 31. März 2015, Axel Beckert wrote:
> > So where is the difference between
> >
> > * setting all files in a binary package to the time stamp defined by
> > the package's changelog entry, and
> >
> > * running a build under a timezone defined by the packag
Hi Axel,
On Dienstag, 31. März 2015, Axel Beckert wrote:
> So where is the difference between
>
> * setting all files in a binary package to the time stamp defined by
> the package's changelog entry, and
>
> * running a build under a timezone defined by the package's changelog
> entry -- or
Hi Chris,
Chris Lamb wrote:
> > * All packages are built with the same timezone.
> >
> > For the reproducible builds project I would have expected that it does
> > the latter already anyways
>
> Just replying quickly; we deliberately don't do this, and in fact
> rebuild twice with opposite timez