Re: [OE-core] [PATCH 1/1] python-xcbgen_1.12: improve reproducibility

2018-04-11 Thread Bystricky, Juro
This would solve the .pyc timestamps problem. However, from reproducibility point of view, it is a bit more desirable to use python-native, as - in principle - different host Python versions can produce different compiled code as well. So it is not the timestamps only. ___

Re: [OE-core] [PATCH 1/1] python-xcbgen_1.12: improve reproducibility

2018-04-10 Thread Burton, Ross
On 6 April 2018 at 20:57, Juro Bystricky wrote: > In order to remove timestamps from all .pyc files we need to recompile > them with python3-native, as we cannot rely on the host python being > able to do that. Both python-native and python3-native derive the timestamp > from SOURCE_DATE_EPOCH if

[OE-core] [PATCH 1/1] python-xcbgen_1.12: improve reproducibility

2018-04-06 Thread Juro Bystricky
In order to remove timestamps from all .pyc files we need to recompile them with python3-native, as we cannot rely on the host python being able to do that. Both python-native and python3-native derive the timestamp from SOURCE_DATE_EPOCH if present. However, building python3-native can be computat