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

Re: A proposed solution for svn admin directory names

From: Branko Čibej <brane_at_xbc.nu>
Date: 2005-07-12 13:44:51 CEST

Marcus Rueckert wrote:

>On 2005-07-12 00:05:07 +0200, Branko Čibej wrote:
>
>
>>So: the only reason SVN_WC_ADM_DIR_NAME is public is because "svn
>>import" wants to avoid importing anything that's called ".svn". If we
>>change this definition, then suddenly "svn import" (and probably add,
>>and others) _could_ end up importing the ".svn" dir.
>>
>>All of which convinced me that we should deprecate SVN_WC_ADM_DIR_NAME,
>>and replace all its uses outside libsvn_wc (which, not surprisingly, are
>>all string compares against this constant) with calls to a new function
>>in libsvn_wc, e.g., svn_wc_is_adm_dir(const char*).
>>
>>Then we can deal with using different admin dir names privately inside
>>libsvn_wc, where such decisions belong.
>>
>>
>
>How do you plan to handle the case that someone checks out a working
>copy with svn admin dir set to ".svn" and imports with setting them to
>"_svn" or vice versa?
>
>
Two ways:

    * .svn will always be reserved, regardless of the name you're
      actually using.
    * You would *not* be allowed to choose any name at all, but only
      select froma short list (probably just .svn and _svn). Then we
      could make all of these names reserved.

-- Brane

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jul 12 13:46:43 2005

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