Bug#894476: RCC: provide option to encode EPOCH timestamp

Hi Thomas, > Maybe the solution is then not in rcc but in whatever generate the files > that the qrc that rcc processes refer to. For instance in the case of > ultracopier lrelease could have a mean if generating .qm files with the > same modified timestamp as the .ts file it processes That

Bug#894476: RCC: provide option to encode EPOCH timestamp

On April 3, 2018 10:15:42 PM GMT+01:00, "Lisandro Damián Nicanor Pérez Meyer" wrote: >El mar., 3 de abr. de 2018 16:42, Sune Vuorela >escribió: > >> On Tuesday, April 3, 2018 9:24:58 PM CEST Chris Lamb wrote: >> > I'm not /entirely/ sure what the

Bug#894476: RCC: provide option to encode EPOCH timestamp

El mar., 3 de abr. de 2018 16:42, Sune Vuorela escribió: > On Tuesday, April 3, 2018 9:24:58 PM CEST Chris Lamb wrote: > > I'm not /entirely/ sure what the difference is as I'm not in the > > Qt/RCC world too often these days (alas !), but why just not use > > SOURCE_DATE_EPOCH

Bug#894476: RCC: provide option to encode EPOCH timestamp

On Tuesday, April 3, 2018 9:24:58 PM CEST Chris Lamb wrote: > I'm not /entirely/ sure what the difference is as I'm not in the > Qt/RCC world too often these days (alas !), but why just not use > SOURCE_DATE_EPOCH *iff* it is exported? > > Normal systems simply do not have this envvar set, so

Bug#894476: RCC: provide option to encode EPOCH timestamp

On April 3, 2018 8:20:22 PM GMT+01:00, Sune Vuorela wrote: >On Tuesday, April 3, 2018 9:14:23 PM CEST Chris Lamb wrote: >> Hi Sune! >> >> > I don't think honouring SOURCE_DATE_EPOCH is the right idea under >normal >> > circumstances >> >> Can you elaborate on what you mean by

Bug#894476: RCC: provide option to encode EPOCH timestamp

Hi Sune, > "normal circumstances" is rcc on a source file, as opposed > to an autogenerated file I'm not /entirely/ sure what the difference is as I'm not in the Qt/RCC world too often these days (alas !), but why just not use SOURCE_DATE_EPOCH *iff* it is exported? Normal systems simply do not

Bug#894476: RCC: provide option to encode EPOCH timestamp

On Tuesday, April 3, 2018 9:14:23 PM CEST Chris Lamb wrote: > Hi Sune! > > > I don't think honouring SOURCE_DATE_EPOCH is the right idea under normal > > circumstances > > Can you elaborate on what you mean by "normal circumstances"? :) "normal circumstances" is rcc on a source file, as opposed

Bug#894476: RCC: provide option to encode EPOCH timestamp

Hi Sune! > I don't think honouring SOURCE_DATE_EPOCH is the right idea under normal > circumstances Can you elaborate on what you mean by "normal circumstances"? :) How about e use S_D_E if it is setup/exported, otherwise use the mtime of the file as before? (This is the pattern/logic used

Bug#894476: RCC: provide option to encode EPOCH timestamp

On Tuesday, April 3, 2018 8:46:51 PM CEST Thomas Preud'homme wrote: > The problematic files are Qt message files (ie .qm files) generated at build > time via lrelease from translation files (ie .ts files). Therefore two Right. I didn't think about autogenerated files during build. > I think it

Bug#894476: RCC: provide option to encode EPOCH timestamp

On Saturday, March 31, 2018 12:05:02 PM CEST Chris Lamb wrote: > > While investigating ultracopier's lack of build reproducibility, I found > > out that rcc encodes the timestamp of the files the QRC file being > > compiled references I don't actually see why this should be a problem. If input

Bug#894476: RCC: provide option to encode EPOCH timestamp

On April 3, 2018 7:25:03 PM GMT+01:00, Sune Vuorela wrote: >On Saturday, March 31, 2018 12:05:02 PM CEST Chris Lamb wrote: >> > While investigating ultracopier's lack of build reproducibility, I >found >> > out that rcc encodes the timestamp of the files the QRC file being >> >

Bug#894476: RCC: provide option to encode EPOCH timestamp

Thanks for the bug! And sorry for the to posting :-( I'll try to take a look into this. El sáb., 31 de mar. de 2018 07:09, Chris Lamb escribió: > Hi, > > > While investigating ultracopier's lack of build reproducibility, I found > > out that rcc encodes the timestamp of the

Bug#894476: RCC: provide option to encode EPOCH timestamp

Hi, > While investigating ultracopier's lack of build reproducibility, I found > out that rcc encodes the timestamp of the files the QRC file being > compiled references Indeed, we've been tracking this for a while in the Reproducible Builds project [0] but, without a patch, we did not wish to

Bug#894476: RCC: provide option to encode EPOCH timestamp

Package: qtbase5-dev-tools Version: 5.9.2+dfsg-12 Severity: wishlist Tags: upstream User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps toolchain Hi, While investigating ultracopier's lack of build reproducibility, I found out that rcc encodes the timestamp of the files the