Re: preserve modification date on co?

On Sep 9, 2004, at 19:57, Harald Dunkel wrote:
>> 'svn co/up' touches each file with 'now', so that tools like 'make'
>> work
>> correctly.
> Who said that make works better if SVN breaks the modification
> date of all files? Don't you assume here that the make target
> (e.g. a library or a lex header file) is not checked in? This
> would be a very severe restriction.
+1

We ran into exactly the same issue when migrating OpenGroupware.org
from CVS to Subversion. Besides lex/yacc stuff this also breaks
pregenerated configure scripts, config.h files etc.

As mentioned in the thread the issue is that on checkout systems the
tools to build such files are likely to be different/incorrect, which
is why this kind of "derived sources" is usually checked into CVS and
only generated by a maintainer.

Of course this issue can be ignored and isn't a catastrophe (at least
not for us ;-), but it certainly a noticable annoyance.

best regards,
   Helge

PS: I don't understand why the question of permissions was brought up?
Thats an completely unrelated topic. Modification dates are portable.

-- 
http://docs.opengroupware.org/Members/helge/
OpenGroupware.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org