Re: A proposed solution for svn admin directory names

On 7/12/05, Branko Èibej <brane@xbc.nu> wrote:> Charles Bailey wrote:> > >On 7/11/05, Branko Èibej <brane@xbc.nu> wrote:> >===================================================================> >> >> >>--- subversion/include/svn_wc.h (revision 15318)> >>+++ subversion/include/svn_wc.h (working copy)> >>@@ -337,6 +337,15 @@> >> apr_pool_t *pool);> >>> >>> >>+/**> >>+ * Return @c TRUE if @a name is the name of the WC administrative> >>+ * directory (usually ".svn"). Use @a pool for any temporary allocations.> >>+ *> >>+ * @since New in 1.3.> >>+ */> >>+svn_boolean_t svn_wc_is_adm_dir (const char *name, apr_pool_t *pool);> >>> >>> >> >Is it worthwhile tomake svn_wc__adm_path() public as well, so that a> >hypothetical tool layered on Subversion can find the admin dir to add> >its own files?> >> >> I don't think that's safe. We'd have to introduce some kind of global> tool registry in order to avoid name clashes in the adm directory, and> that's flaky at best.
Fair enough, though it'd also be nice to avoid proliferation of admindirs. As an alternative, perhaps you'd want to let the applicationset the admin dir (on its own head be it if it changes valuesmid-stream or doesn't take care of thread safety), to allow for tool"foo" built on the Subversion APIs to make .foo its admin dir, andtell Subversion to use .foo/svn.

-- Regards,Charles BaileyLists: bailey _dot_ charles _at_ gmail _dot_ comOther: bailey _at_ newman _dot_ upenn _dot_ edu
Received on Tue Jul 12 19:26:16 2005