Re: Files in repository but not version controlled

On Fri, 2006-09-22 at 05:09, Jeremy Pereira wrote:

> >> I think this is an extremely dangerous idea because there is no
> >> guarantee that the HEAD revision of the generated files are the
> >> ones that relate to the HEAD revision of the source files.
> >
> > I fail to see the extreme danger. And if you serve generated files
> > separately, outside the repository, there is no guarantee either
> > that they relate to the HEAD revision.
>
> You don't see the problems that might ensue if your documentation
> doesn't match your code?

The real question is, how is it more dangerous for subversion
to handle files defined as unversioned in a predictable
way than for everyone who needs the facility to have to
write their own ad-hoc mechanism? I think it would be
better to have the mechanism than not, but the danger
I see is that enabling it should really be an administrative
function - that is, you should not permit just anyone to
set it on random files and have it quietly throw away
the history that other users think it is saving.

> And if you are automating a checkout and build, surely it is not
> beyond your capability to automate deletion of the intermediate build
> products.

Just because every developer can write a new, wonderful and
bug-free way to do every operation doesn't mean it is a good
idea.

-- 
  Les Mikesell
   lesmikesell@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org