[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Unversioned files held by repo

From: Reedick, Andrew <jr9445_at_ATT.COM>
Date: Wed, 12 Mar 2008 12:40:41 -0500

> -----Original Message-----
> From: Les Mikesell [mailto:lesmikesell_at_gmail.com]
> Sent: Wednesday, March 12, 2008 12:34 PM
> To: Paul Koning
> Cc: madscientist343_at_gmail.com; andy.levy_at_gmail.com;
> users_at_subversion.tigris.org
> Subject: Re: Unversioned files held by repo
>
> >
> > Then again, it strikes me that what you're proposing is positively
> > evil -- something that goes directly against what any source control
> > system should do. The whole point of source control is to be able
to
> > see history. The mechanism you describe specifically aims to
destroy
> > history. This is bad. Subversion must not consider ever doing such
> a
> > thing.
>
> 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. It breaks build repeatability.
Specifically, how would you roll back or otherwise deploy a previous
build/deployment if the disposable files are not being tracked?

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.

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.

Plan B.1 would be to attach unversioned revision properties to revision
1 of the archive. The user would run a script to pull in the unversioned
files listed in the revision property. If there are no limits to the
size of an unversioned revision property, you could in theory, attach
entire files as properties... Properties containing entire files would
make it easy for the script to update a workspace's disposable files.

*****

The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential, proprietary, and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from all computers. GA621

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-03-12 18:41:46 CET

This is an archived mail posted to the Subversion Users mailing list.