To this point ... I was reading how the development environment of some=20
opensource project (debian?  ubuntu?) was delivered as ... an entire=20
virtual machine "image", to run in a VM "player".  So all the tools=20
(compiler and little command-line binaries) and shell settings are=20
delivered instant ready to run, for everyone.  Wow.  Cuts the whole "I=20
can't get it to build what's wrong with my settings/versions" thing=20
right out.

Made me think that would be a good (if perhaps overkill in most=20
instances) way to preserve the State of Things at important moments of=20
time, to be able to replicate bugs discovered years hence as needed, and=20
to be able to do tiny surgical fixes of such with exactly the same=20
toolset that made the final release way back when in 2011.

Neato.

Cheers,
J


Isaac Marino Bavaresco wrote:
> Em 4/3/2011 21:51, William "Chops" Westfield escreveu:
>> On Mar 4, 2011, at 4:55 AM, Isaac Marino Bavaresco wrote:
>>
>>> The repository must contain *everything* necessary to build the final
>>> product, except the build tools themselves.
>> That "except the build tools themselves" is a huge hole in your
>> philosophy, and a big part of what I was talking about.
>
> The paragraph you snipped out changes things a little:
>
> "I always keep back-ups of the installers for every version of the build
> tools I ever used and keep a note on the source files saying what build
> tools and versions were used."
>
>
> Remember that the executables are usually kept on system-specific
> directories, it would be hard to keep them on the same tree with the
> sources. Besides, to restore a software product is usually not simply a
> matter of copying some files to a directory.
>
>
> Isaac
>
--=20
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.