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

Re: maintaining a list of svn: revprops

From: Karl Fogel <kfogel_at_google.com>
Date: 2006-08-22 08:24:43 CEST

Eric Gillespie <epg@pretzelnet.org> writes:
> Karl Fogel <kfogel@google.com> writes:
>> "C. Michael Pilato" <cmpilato@collab.net> writes:
>> > As a community, we could probably stand to carefully consider this idea of
>> > the Subversion core system. I mean, honestly, why are svnversion and
>> > svnsync in the main source tree while mailer.py and svnmerge.py (which also
>> > uses custom properties) relegated to the tools/ directory. Simply because
>> > they aren't written in C? These might be healthy questions to entertain.
>>
>> I think you might have an unorthodox interpretation of our source tree
>> layout.
>>
>> Stuff in tools/ *is* in the main source tree, and is a supported part
>> of Subversion.
>
> make install still doesn't install them, right? That makes
> tools/ a ghetto. I feel the same way about the bindings.

That's true, 'make install' doesn't install them. I don't think
that's because we'd never want to do that, though. It's more that
we've never thought of it, and therefore haven't bothered to give
those tools consistent prefixes or installation procedures.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Aug 22 08:26:19 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.