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

'SVN' to '.svn' WAS: RE: Successful bootstrap on Mac OS X

From: Sander Striker <striker_at_apache.org>
Date: 2001-09-03 16:10:48 CEST


> Greg Stein wrote:
>> On Sun, Sep 02, 2001 at 05:52:26PM +0200, Dominik Westner wrote:
>> Hi,
>> I am not sure if this is the correct mailing list, but I just wanted to
>> tell you, that I was able to compile subversion-M3 on Mac OS X 10.04.
>> I then checked out subversion from the repository and compiled it again.
>> It also ran all tests successfully and I was able to upgrade to version
>> 22
> Cool :-)
> [ and yes, it is the correct list ]
>> I had the following problems when compiling:
>> --with-berkeley-db=/usr/local/BerkeleyDB.3.3 does not seem to work, I
>> had to create a link from the db sources to db
> Hmm. Can you locate the relevant section of your config.log and post that?
> Or better yet: figure out why it didn't like that path?

I had the same problem. Haven't figured out what it is yet. The configure
script claims to be looking in '/opt/db' for 3.3.11, but isn't finding it,
although it is installed there. FYI, this is with the M3 tarball on a
linux 2.4.3 system. I haven't tried the checked out copy with an external
db path yet.

> > Mac OS X uses a case insensitiv file system, when it tries to link the
> > svn program it will the linker will throw an error that the file is
> > already existing as a directory. The SVN directory is in the way. I
> Urf. Never thought of that one :-)

*grin* Case sensitivity is something that people running *nix most of
the time tend to forget.

> > tried to use the --program-suffix=SUFFIX option, but the option seems
> > to be ignored.
> Yup. I took it a look. It is ignored... Can you provide a patch? I'd think
> you would want to AC_SUBST(program_suffix) into the Makefile, then tweak
> gen-make.py to append $(program_suffix) on the end of executable
> names when it generates a LINK line.
> > Workaround: move the SVN directory out of the way.
> >
> > Wouldn't it be better in general to use .svn or .SVN instead of SVN?
> I like .svn. The only reason we have SVN for the name is a legacy
> similarity to CVS. I can't really think of a reason to keep them

I personally don't think we need to stay in the CVS mindset. If it would
count I would vote +1 for moving from "SVN" to ".svn". It is only 1 #define
And possibly a quick directory rename script for the developers.



To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:39 2006

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.