D25494: Make tar archives reproducible by setting Pax headers

[Aaron Puchert]

aaronpuchert added a comment.


  In D25494#592751 <https://phabricator.kde.org/D25494#592751>, @bmwiedemann wrote:
  
  > This should work fine with a producer GNU-tar >= 1.28
  
  
  We use the option only when `SOURCE_DATE_EPOCH` is set, and we assume that a recent enough tar is available then. Basically we say that if reproducible builds are desired, the proper tools should be available.
  
  > what will be the consumer of the tar file?
  
  Not sure I understand this question. The archive is created as part of the build process and then installed, on most Linux distributions into `/usr/share/kdevappwizard/templates`.
  
  > Asking because I remember the case of alpine Linux and its 'abuild' producer. Alpine package manager implemented its own tar and that would only be happy with
  > 
  >   --pax-option=exthdr.name=%d/PaxHeaders/%f,atime:=0,ctime:=0
  
  Does this mean it won't be happy with `delete=atime,delete=ctime`? And what does it mean that the package manager has its own tar, is this is a different tar than is used in the distribution itself?
  
  > The other thing is about POSIXLY_CORRECT - it is only considered in recent tar git (no releases last time I checked) and only for embedding the PID of the tar process. So I would just not mention it in the commit message to make it easier to understand:
  
  The change is already committed, so I can't change the message anymore. I didn't know you were here, otherwise I would have added you earlier as reviewer.

REPOSITORY
  R32 KDevelop

REVISION DETAIL
  https://phabricator.kde.org/D25494

To: aaronpuchert, kfunk, #kdevelop, kossebau
Cc: bmwiedemann, kossebau, kdevelop-devel, hmitonneau, christiant, glebaccon, domson, antismap, iodelay, alexeymin, geetamc, Pilzschaf, akshaydeo, surgenight, arrowd
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20200114/046a1a84/attachment-0001.html>