On Wed, Mar 12, 2008 at 11:41 AM, Les Mikesell <lesmikesell_at_gmail.com>
wrote:
> Erik Huelsmann wrote:
> >
> > Subversion supports that model by not making more copies of a file
> > than necessary: all revisions for which a file is the same share
> > storage. So, for files which change infrequently, you shouldn't be
> > hesitant to store them in your repository.
>
> But... there are files that do change frequently and files where old
> instances have no use at all - and it would still be nice to be able to
> use subversions's access mechanisms to store and distribute them. And,
> of course, it would be nice to have a reasonable way to undo accidental
> commits of things that don't belong in the repository at all or can't
> remain for legal or political correctness reasons.
As an example I am working on a project that requiers an expensive and
proprietary compiler(not by choice) and as the only coder on the project
currently I am the only one with who is able to compile the files need to
use the program. I was disapointed when I found I could not keep a compiled
binary with the revision I checked in which could later be removed as the
repo size expanded and older binaries were no longer needed and free space
declined. The folder layout is already set by a 3rd party and would work
very well if unversioned files were able to be distributed with svn commit
and svn update to the other people working on the project.
>
>
> --
> Les Mikesell
> lesmikesell_at_gmail.com
>
>
Received on 2008-03-12 18:27:07 CET