On Thursday, 16. February 2006 16:41, Kevin Greiner wrote:
> On 2/16/06, Lars Heineken <lars.heineken@diasemi.com> wrote:
> >
> >
> > I'm looking for a way to turn off revisioning of certain files without
> > taking them out of the repository. Background is that we are using
> > subversion to distribute library files that take up a lot of space,
> > especially on the subversion server. As backup space for the repository
> > on the server is running out we want to keep the repository as small as
> > possible but not sacrifice the automatic distribution of changes across
> > all worspaces. Is there a way to just turn off versioning on a file ?
> > I have looked through the documentation but found no trace of such a
> > possibility.
> >
>
> No, this is not a current feature although it has been requested before for
> use in situations similar to your own.
We have a similar problem...
> How is this feature is essential to a "version control system?" Why not use
> a file system for distributing large binary files?
Perhaps because that would require to set up another "distribution system" with access control and everything plus requiring the users to use two retrieval systems.
In our case, there are 2 methods to access the subversion server, depending from where:
- from the internet: svn only.
- from internal: https only.
Maybe I could setup a rsync server in addition to the subversion server and the web server. Hmmm...
Furthermore, I can imagine that a certain "version" of a library should be distributed along with some other stuff that is, indeed, versioned.
If the file-to-distribute is compressed, subversion's ability to make binary deltas wouldn't help to minimize storage consumption, too.
Having versionless files would really be a nice feature.
Due to the lack of it, I was planning to try/use a "brute force" solution:
Set up a certain repository, only for the "versionless" file (permissions and everything around can be copied (and adjusted) from another repository). Check in the versionless file. Now, when there is a change to that file: *Wipe out* the content of the repository and checkin the new version.
This way, there will be only one revision at a time and remote users can still the subversion access method to get it.
But there is no relation to other (really versioned) files, so this is only a makeshift, compared to a possible ability of subversion to declare a file as versionless and always replace it, instead of keeping/maintaining a history...
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Feb 20 13:32:00 2006