buildroot snapshot
Hi All,
Could someone confirm (or not) my understanding of how a snapshot works when used at a later date. I have looked at sources and read the docs but I still do not have a definitive answer.
I am using buildroot-20080428 snapshot on my current development box. If I install this same snapshot on another machine today [and configure for the same target] would it be reasonable to expect the same toolchain & other bits [kernel, file system(s) etc] to be identical
(again, assuming identical .config files). I believe this to be the case.
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.
Regards,
Mike
Quoted 3 lines
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.
Quoted 11 lines · Thiago A. Corr?a
Quoted 4 lines
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
Quoted 6 lines
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Scanned with Copfilter Version 0.84beta3a (P3Scan 2.2.1)
AntiSpam: SpamAssassin 3.2.3
by Markus Madlener @ http://www.copfilter.org
Quoted 15 lines · Mike Sander
Quoted 11 lines · Thiago A. Corr?a
Quoted 4 lines
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.
Quoted 6 lines
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.
Backups ;-)
If you are using a vanilla buildroot without modifications, you can download the latest svn or you can download a previous version of buildroot (read subversion documentation to find out how)
It is highly unlikely that a default configuration will be OK for you. You should write down which version of buildroot you are using, and you need to store somewhere the configuration you are using and any modifications to the buildroot tree.
Periodically backing up the source tarballs may be helpful.
Quoted 11 lines
Regards,
Mike
Quoted 6 lines
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Scanned with Copfilter Version 0.84beta3a (P3Scan 2.2.1)
AntiSpam: SpamAssassin 3.2.3
by Markus Madlener @ http://www.copfilter.org
Quoted 4 lines
_______________________________________________
buildroot mailing list
buildroot at uclibc.org
http://busybox.net/mailman/listinfo/buildroot
Best Regards
Ulf Samuelsson
Quoted 34 lines · Ulf Samuelsson
Quoted 17 lines · Mike Sander
Quoted 5 lines · Thiago A. Corr?a
Quoted 5 lines
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.
Quoted 7 lines
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.
Quoted 7 lines
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.
Backups ;-)
If you are using a vanilla buildroot without modifications, you can download the latest svn or you can download a previous version of buildroot (read subversion documentation to find out how)
Quoted 8 lines
It is highly unlikely that a default configuration will be OK for you. You should write down which version of buildroot you are using, and you need to store somewhere the configuration you are using and any modifications to the buildroot tree.
Periodically backing up the source tarballs may be helpful.
No I'm not using a vanilla buildroot anymore. Backing up modified
bits & backing up tarballs... all good ideas.
Thank You for the tips.
Mike
Quoted 28 lines
Quoted 11 lines
Regards,
Mike
Quoted 7 lines
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Scanned with Copfilter Version 0.84beta3a (P3Scan 2.2.1)
AntiSpam: SpamAssassin 3.2.3
by Markus Madlener @ http://www.copfilter.orgQuoted 5 lines
_______________________________________________
buildroot mailing list
buildroot at uclibc.org
http://busybox.net/mailman/listinfo/buildrootBest Regards
Ulf Samuelsson=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Scanned with Copfilter Version 0.84beta3a (P3Scan 2.2.1)
AntiSpam: SpamAssassin 3.2.3
by Markus Madlener @ http://www.copfilter.org