RE: What is the .svn/empty-file for?

> > > But I admittedly was thinking of only unix-like and windows...I'd
> > > forgotten the "any APR supported system" idea. (Is that
> > really true?
> > > Is anybody *really* running Subversion on Netware. Would it work?)
> >
> > APR has been ported to AS/400 + OS/400; Subversion porting is
> > on the way. No idea if it's unix like enough, but there
> > really is a wide range of systems on which Subversion is being used.
> >
> >
> > bye,
> >
> > Erik.
> >
> > PS: Thanks! Nice to know NUL: behaves unix-like enough to be
> > the functional equivalent of /dev/null.
>
> OK, I can see how there is a portability problem. But as a suggestion,
> is it possible to put a single empty file in the root of the working
> copy? Or, better yet, put one in the install location of subversion
> itself? That way, all repositories on a machine have acess to an emtpy
> file, without requiring /dev/null to exist/be portable/etc. Or am I
> missing something?

Only one file in the top of the checkout is not an option, because every
subdir is a valid checkout by itself. You can copy any subdir to a new
location and use it as a top dir there.

Maybe it's worth the change to start using /dev/null or NUL now and ditch
the .svn/empty files as soon as a major working copy change comes by. I'll
need to investigate how easy that is.

bye,

Erik.

-- 
+++ Sparen Sie mit GMX DSL +++ http://www.gmx.net/de/go/dsl
AKTION für Wechsler: DSL-Tarife ab 3,99 EUR/Monat + Startguthaben
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org