Re: Ignoring versioned Files/Folders

On Nov 22, 2007 1:23 PM, Blackwell <blackwell@nexgo.de> wrote:

> I have read what has been said in the past about ignoring versioned
> files, that they shouldn't be versioned in the first place and that
> the file should be added under a different name, as a template, to
> be modified in every checked, manually or via script.
>
> I like to present a few arguments against this (oddly puristic)
> point of view (I also added this as a feature request to the
> subversion issue tracker, issue 3028, but since we are using
> TortoiseSVN exclusively I would be helped with support for this in
> TortoiseSVN already):

You really ignored the big yellow/red warning on the svn issue tracker page?
Tough choice - prepare to get flamed... :)

> From the FAQ: "I have a file in my project that every developer
> must change, but I don't want those local mods to ever be committed.
> How can I make 'svn commit' ignore the file?"
>
> The suggested solution is to use platform specific scripts to
> "initialize" the working copy/checkout.

Why? Why platform specific scripts?

> This is however platform specific and requires maintenance effort.

Again: why?
I can write platform independent scripts as easy as platform specific ones.
Can't you?

> This is also impractical for a large number of files which are not
> to be checked in.

'large number of files' used as templates? I think in that case we can
safely assume that your build process is "a good candidate for major
optimization and cleanup" (ok, I could use some other phrase here, but
I think you get the point).

> For example we have a complete Eclipse instance in our svn
> repository and we want to ignore every change in its directory and

Sorry, what? Maybe I'm misunderstanding, but do you really have the
whole Eclipse binaries under version control?

> Also, when the user forgets to run the init script after a checkout
> (and possibly after an update, which might add further files that
> must be renamed for things work properly) applications might
> misbehave when they do not find their expected files.

Yes, that's expected: applications then should return an error so the
user knows that he forgot something. If however the application just
doesn't work properly: take this as an opportunity to find bugs :)

It's not documented yet but already in use by some people:
http://svn.haxx.se/tsvn/archive-2007-07/0335.shtml

Stefan

-- 
       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org