From: Mike Sander <msander@ripnet.com>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot snapshot
Date: Tue, 24 Jun 2008 00:51:40 -0400 [thread overview]
Message-ID: <48607D5C.2040002@ripnet.com> (raw)
In-Reply-To: <d6cda7730806231936n7211fd34h929fead0f5ef220a@mail.gmail.com>
Thiago A. Corr?a wrote:
>> I guess I am looking for confirmation that the snapshot contains
>> specific versions of packages and patches, and these same ones will be
>> used even if the snapshot is run at a later date.
>>
>
> Yes. Although sometimes packages vanish from their download sites for
> whatever reason. In that case, you might be forced to bump versions or
> update URLs in .mk files. That's unavoidable, unless you save/mirror
> your download folder.
>
>
Thank You for the confirmation. Good point about specific bits
disappearing. I'll be sure to archive these.
As we move from development to production stability and repeatability
become more critical.
I have also been thinking about this in the context of "what if one of
my development boxes dies?" ... what do I need to do to get back to a
working system.
Regards,
Mike
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> Scanned with Copfilter Version 0.84beta3a (P3Scan 2.2.1)
> AntiSpam: SpamAssassin 3.2.3
> by Markus Madlener @ http://www.copfilter.org
>
>
next prev parent reply other threads:[~2008-06-24 4:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-21 2:12 [Buildroot] buildroot snapshot Mike Sander
2008-06-24 2:36 ` Thiago A. Corrêa
2008-06-24 4:51 ` Mike Sander [this message]
2008-06-24 7:35 ` Ulf Samuelsson
2008-06-25 1:33 ` Mike Sander
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=48607D5C.2040002@ripnet.com \
--to=msander@ripnet.com \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox