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

Re: ".svn" directory name no good (in fact, it is worse than I thought)

From: Files <files_at_poetryunlimited.com>
Date: 2003-09-25 17:36:43 CEST

B. W. Fitzpatrick (fitz@red-bean.com) wrote:
>
>We've been through all of this a *million* times in the last 3.5
>years--the name of the admin directory, why we don't want it
>configurable by a directive... the list goes on... and quite frankly,
>I'm just tired of arguing about it.

I guess I'm just trying to understand it. I'm not saying we have to do
anything. I'm trying to catch up on the reasons why and why not. I guess
I'm not truly seeing the light as far as configurability goes. If it's
configurable, then third party tools could conceivably also be so informed.

>We discuss and discuss and discuss and make a decision and a year later,
>*someone* will have 50 reasons (just as valid) why we should change it
>*back* to .svn. *thud*

LOL

>This isn't directed at you, Shamim--this is just one of the hazards of
>doing Open Source development. *sigh*

Well, for myself, I'm asking questions because I *don't* know the answers.

I'm just wondering if we've got a really valid reason for hardwiring
something that might conceivably make our sphere of influence that much
wider.

I *have* seen some comments about compensating about a vendor's broken
software.

But I haven't seen a lot of advocating adoption by supporting a wider range
of environments.

We're not big enough to narrow our focus too much I'm thinking.

Is it a manpower issue? Is it a design issue?

What are the main arguments for and against beyond "moving working copies"
between locations.

And if you truly are moving *between locations*, is it truly difficult to
envison a

=================================mvadminfrom=========================
Moves wc admin path from one standard to another
Shamim Islam (c) 2003, Licenced under LGPL

You may copy/use/distribute this program for any use covered by the
LGPL as long as the copyright notice is intact and your code abides
by the LGPL and this source is made freely available.

If you did not receive a copy of the LGPL, please to to www.gnu.org for
full text.

mvadminfrom [OPTIONS]

-n - no execution
-o unix|win32 - to OS
-f from admin path override, defaults to .svn on unix, _svn on win32
-t to admin path override, defaults to _svn on unix, .svn on win32
-p root path override - location of wc root to start conversion, defaults
   to .
=====================================================================
#!/bin/bash
function MoveAdminFrom()
{
  # No info, exit
  if [ "$1" == "" ] ; then
    exit;
  fi
  # Test mode - no execution
  if [ "$1" == "-n" ] || [ "$1" == "-N" ] ; then
    TEST=1
    shift
  else
    TEST=0
  fi
  # Default output format -o win32 or -o unix etc
  if [ "$1" == "-o" ] || [ "$1" == "-O" ] ; then
    shift
    if [ "$1" == "win32" ] ; then
      SVNFROM=_svn
      SVNTO=.svn
    else
      SVNFROM=.svn
      SVNTO=_svn
    fi
    shift
  fi
  # Override FROM path
  if [ "$1" == "-f" ] || [ "$1" == "-F" ] ; then
    shift
    SVNFROM="$1"
    shift
  fi
  if [ "$1" == "-t" ] || [ "$1" == "-T" ] ; then
    shift
    SVNTO="$1"
    shift
  fi
  # Path override
  if [ "$1" == "-p" ] || [ "$1" == "-P" ] ; then
    shift
    ROOTPATH="$1"
    shift
  fi
  if [ "$ROOTPATH" == "" ] ; then
    ROOTPATH='.'
  fi
  find "$ROOTPATH" | grep "\\$SVNFROM$" | while read FROMPATH ; do
    SVNTOP=`dirname $FROMPATH`
    if [ $TEST -eq 1 ] ; then
      echo "$FROMPATH" "$SVNTOP/$SVNTO"
    else
      mv "$FROMPATH" "$SVNTOP/$SVNTO"
    fi
  done
}

MoveAdminFrom "$@"
============================end==mvadminfrom=========================

Shamim Islam
BA BS

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Sep 25 17:38:52 2003

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.