[yocto] Yocto & long-term reproducibility of rebuilds

[Gary Thomas]

On 2012-01-30 10:37, Khem Raj wrote:
> On Mon, Jan 30, 2012 at 8:34 AM,<paul_nathan at selinc.com>  wrote:
>> Hi,
>>
>> I am investigating Yocto for a build system here. Part of my requirements
>> for a build system is auditable/traceable builds that can be replicated long
>> into the future (our company has a 10 year warranty on our products, and we
>> build products for the multidecade term). Initial examination of Yocto shows
>> that it builds packages from a number of different domains online, which
>> will not meet our requirements - we'll have to store these packages to
>> ensure these packages exist in the correct version long into the future.  I
>> know we can manually edit the SRC_URI setting in .bb files, but the more
>> general problem of package archiving exists.
>>
>> I am interested in any information or recommendations other users of the
>> Yocto system have on how they have solved this sort of design constraint.
>
> Hi Paul
>
> You can cache all the source tars as you mentioned and then
> store them internally and use PREMIRROR facility which should
> check premirrors before it hits src_uri so provided you cache
> all the sources it should always get it from your internal
> mirror

Check the archives - there was an extensive discussion of this last week
   '[yocto] tar ball vs. git development questions'

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------