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 would be nice if there was a way for
> rcc to avoid doing that manually. I agree with Chris that honouring
> SOURCE_DATE_EPOCH in rcc would be a nice solution.
I don't think honouring SOURCE_DATE_EPOCH is the right idea under normal
circumstances, given that I do think that having the actual timestamp of the
non-generated files makes sense.
I have reached out to upstream about it.
/Sune
--
I didn’t stop pretending when I became an adult, it’s just that when I was a
kid I was pretending that I fit into the rules and structures of this world.
And now that I’m an adult, I pretend that those rules and structures exist.
- zefrank
Reply to: