From: Gary Thomas <gary@mlbassoc.com>
To: yocto@yoctoproject.org
Subject: Re: Yocto & long-term reproducibility of rebuilds
Date: Mon, 30 Jan 2012 10:50:03 -0700 [thread overview]
Message-ID: <4F26D84B.6080709@mlbassoc.com> (raw)
In-Reply-To: <CAMKF1sodYnhvVBt852x4BD8XUP193m7d=DrbNrN3-GHJ6E8q_w@mail.gmail.com>
On 2012-01-30 10:37, Khem Raj wrote:
> On Mon, Jan 30, 2012 at 8:34 AM,<paul_nathan@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
------------------------------------------------------------
next prev parent reply other threads:[~2012-01-30 17:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-30 16:34 Yocto & long-term reproducibility of rebuilds paul_nathan
2012-01-30 17:37 ` Khem Raj
2012-01-30 17:50 ` Gary Thomas [this message]
2012-01-30 18:10 ` Frans Meulenbroeks
2012-01-30 18:34 ` Flanagan, Elizabeth
2012-01-30 20:10 ` Chris Tapp
2012-01-30 21:36 ` Richard Purdie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F26D84B.6080709@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.