> Here is exactly another case where "unversioned files" would be the ruin
> of anyone using them. Suppose you build at r10, and add the binary to
> the tree. Then 10 revisions later, you build again. Now say _someone
> else_ wants to go back and run the program as existed in r10. THEY CANT
> because they will get the binary from r20!
You are right this doesn't help with all cases. Though you could rename the
binary or put them each in a folder with the revision number to keep them
separate. Wouldn't it be better to have at least the latest binary in there
then nothing at all? ( if you cant remove the files regularly( easily ) and
don't have space for each change then you cant include them at all... ) As a
note this would not stop anybody from versioning all the files including the
binaries, it is only giving the people who maintain/use the repo more
options to choose from.
Received on 2008-03-12 21:37:37 CET