Hi, Jérémy Bobbio wrote: > Guillem Jover:
>> For example, in the generated data.tar the files will contain >> different modification times, some will come untouched from the source >> files if they just get copied, and others will be newer if the files >> got created at build time. Preserving these timestamps seems important >> to me, because you then know the possible staleness of the files. > > I disagree that this is important information. Most packages that I have > seen so far do not propagate timestamps when copying a file from source. > Could you give me an example of one that would do so? See http://www.debian.org/doc/debian-policy/ch-source.html#s-timestamps [...] >> Possible future ar members containing gpg signatures from the builder >> or the archive, would change and not be reproducible anyway. The recent >> switch of dpkg-deb default compressor. Or possible future .deb format >> revisions. Etc. > > Could you please elaborate? The idea is to record list of packages that > has been initially able to build the package and to reinstall exactly > the same set of packages (from snapshot.d.o) when performing rebuilds. That can be problematic when packages used during the build get security fixes, fixes for new hardware support, and so on. Not to mention sources of randomness during the build, such as parallelism. But I don't want to discourage you --- it's an interesting project, even if I think it's a doomed one. ;-) Thanks, Jonathan -- To UNSUBSCRIBE, email to debian-dpkg-bugs-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
