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

RE: Re: RFE: new kind of unversioned files

From: Daniel Becroft <Daniel.Becroft_at_supercorp.com.au>
Date: Thu, 8 May 2008 12:34:09 +1000

NOTE: Always "Reply To All" to ensure the message gets delivered to the
entire group.

> -----Original Message-----
> From: fkater_at_googlemail.com [mailto:fkater_at_googlemail.com]
> Sent: Wednesday, 7 May 2008 6:56 PM
> To: Daniel Becroft
> Subject: Re: Re: RFE: new kind of unversioned files
>
> Daniel Becroft:
>
> > > (b) Wouldn't it be useful e.g. for programmers to include binary
> > > libraries (DLLs, whatever) into the repository (without version
> > > control!) to pass the latest version only to the others without
> > > forcing them to build the libraries?
> >
> > True, but what happens if the users need to use a previous revision?
>
> I am thinking of a case where users explicitly do NOT want
> previous revisions -- for various reaaons as mentioned.

The correct way to go, if you need to include this information, is to
version it.

For example:

Version 1.0 of a Project uses version 2.2.3 of a particular binary file
(DLL/JAR)
Version 1.1 of same Project uses Version 2.3.0 of the same binary file
(DLL/JAR) - this one has non-backwards compatible API changes

What is gained by replacing ALL versions of the binary file with V2.3.0?
If a user then checks out V1.0 of the application (for testing, etc),
then it bcomes unusable because they now have the new, incompatible
binary.

> The reasons not to use versioning on these files might be
> completely the same why users mark files 'unversioned' with
> the current version of svn.

Actually, no. They are two complete different concepts. The current
definition of "unversioned" is a file that has not yet been added to the
repository. Your use case is basically "remove the previous revision in
which these files were added, then add them in again in a new
revision.".

> The only difference I wanted to point to is: Having an option
> to still put these files into the repository to keep them at
> the right place in your tree, to use centralization and
> distribution of files etc... :-)

It is still unclear as to why having these files versioned is a bad
thing? Whichever way it is done, whenever those files are changed, there
is going to be a hit when a user does an "Update".

Cheers,
Daniel B.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-05-08 04:31:50 CEST

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