Re: [Reproducible-builds] lua-ldoc --date/SOURCE_DATE_EPOCH
p...@passoire.fr: > Hi Ximin. > > Le 06/04/2016 13:17, Ximin Luo a écrit : >> The most preferable route would be to persuade upstream to accept patch (2). >> If they don't do that, then it's still worth doing option (2) over (1) > > Thanks for your answer. I will go the SOURCE_DATE_EPOCH way. > > How can I handle debian/upstream duality? I mean if I send a patch > proposal upstream, maybe it would be better to also open a bug in > debian, so that if someone works on reproducibility he won't do the work > independently from me? > Or I can send a patch to the debian package maintainer, that he can pass > upstream: this way I won't bypass him? > Best to open both - i.e. open the upstream one first, then open a debian one with the pseudo-headers "forwarded -1 " and "tags -1 + upstream". You might need to prepend "Control: " depending on how you're submitting the bug report, see https://www.debian.org/Bugs/server-control for more details. X -- GPG: ed25519/56034877E1F87C35 GPG: rsa4096/1318EFAC5FBBDBCE git://github.com/infinity0/pubkeys.git ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
Re: [Reproducible-builds] lua-ldoc --date/SOURCE_DATE_EPOCH
Hi Ximin. Le 06/04/2016 13:17, Ximin Luo a écrit : > The most preferable route would be to persuade upstream to accept patch (2). > If they don't do that, then it's still worth doing option (2) over (1) Thanks for your answer. I will go the SOURCE_DATE_EPOCH way. How can I handle debian/upstream duality? I mean if I send a patch proposal upstream, maybe it would be better to also open a bug in debian, so that if someone works on reproducibility he won't do the work independently from me? Or I can send a patch to the debian package maintainer, that he can pass upstream: this way I won't bypass him? Thanks, Alexis. ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
Re: [Reproducible-builds] lua-ldoc --date/SOURCE_DATE_EPOCH
Alexis Bienvenüe: > Hi. > > lua-ldoc's maintainer added a --date option that helps reproducible > building. It is used by lua-penlight. > However, awesome and lua-posix don't use it already. > > What should you recommend? > 1) patch awesome and lua-posix to use --date > 2) patch lua-ldoc to add SOURCE_DATE_EPOCH, on top of --date. This would > be more reliable, but maybe lua-ldoc will get a little messy/muddled? > > Thanks for your advice, > Alexis Bienvenüe. > Hi Alexis, One of the motivation factors for SOURCE_DATE_EPOCH was to have a *standardised* method for build tools to use - i.e. O(1) effort - instead of every tool inventing their own special command line flag that then every distribution each has to know about - i.e. O(m * n) effort. The most preferable route would be to persuade upstream to accept patch (2). If they don't do that, then it's still worth doing option (2) over (1) because other tools in Debian at least can rely on this standard, instead of hard-coding lua-ldoc-specific logic everywhere. Hope that makes sense, Ximin -- GPG: ed25519/56034877E1F87C35 GPG: rsa4096/1318EFAC5FBBDBCE git://github.com/infinity0/pubkeys.git ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
[Reproducible-builds] lua-ldoc --date/SOURCE_DATE_EPOCH
Hi. lua-ldoc's maintainer added a --date option that helps reproducible building. It is used by lua-penlight. However, awesome and lua-posix don't use it already. What should you recommend? 1) patch awesome and lua-posix to use --date 2) patch lua-ldoc to add SOURCE_DATE_EPOCH, on top of --date. This would be more reliable, but maybe lua-ldoc will get a little messy/muddled? Thanks for your advice, Alexis Bienvenüe. ___ Reproducible-builds mailing list Reproducible-builds@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/reproducible-builds
