Re: Unversioned files held by repo

Reedick, Andrew wrote:
>
>> Except that preserving all history of everything forever is
> impractical
>> and at some point becomes impossible and will thus cause you to lose
> it
>> all. So it is not as evil as you might think to be selective about
>> what
>> you keep.
>
>
> No, it is Evil as per FDA standards.

But consider a likely alternative, where you run the repository out of
space because you can't delete just to maintain unwanted disposable
and/or reproducible content. Or on the opposite site you have people
who avoid committing things because of the side effects that can't be
undone.

> It breaks build repeatability.

A likely scenario is that the items in question are build targets, not
dependencies, but you'd like them stored temporarily or for others to be
able to access them without having to build their own.

> Specifically, how would you roll back or otherwise deploy a previous
> build/deployment if the disposable files are not being tracked?

The same way you'd do it in the current situation where you never commit
those files at all.

> Plan B would be to check the disposable files into a separate disposable
> repository (or put them on a file server.) Users would check out from
> the main repository and then run a script to pull the data from the
> disposable repository/file server into their workspace. The disposable
> repository could be wiped as needed.

That's sort-of workable, but only if they can live in separate directories.

> It's the best of both worlds, but you would need to write wrapper
> scripts for 'svn co' and 'svn update' to make it easy for people to pull
> the disposable files in.

Having to write scripts for each file doesn't sound all that easy to me.

-- 
   Les Mikesell
     lesmikesell_at_gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org