That file is (potentially) out-of-date. The canonical location for this file is now:
http://svn.apache.org/repos/asf/subversion/trunk/subversion/bindings/swig/INSTALL
-Hyrum
On Nov 22, 2009, at 9:06 PM, David Weintraub wrote:
> You also need the C based Subversion API as well as this module. This
> might be helpful:
> http://svn.collab.net/repos/svn/trunk/subversion/bindings/swig/INSTALL
>
>
> On Fri, Nov 20, 2009 at 9:55 AM, TSR <svn_at_trodman.com> wrote:
>> Thanks for your help!
>>
>> On Wed 11/18/09 11:20 EST David Weintraub wrote:
>>> There is a Perl Subversion API, and a quick look at CPAN reveal this
>>> Perl module: http://search.cpan.org/~mschwern/Alien-SVN-1.4.6.0/.
>>
>> I have been looking that over (otherwise
>> known as SVN::Client I think). As far as I see this module
>> is not included w/subversion (at least not mine). I tried
>> to build it under centos 5.3 and ran into problems - these
>> comments (on the build steps)
>> http://rt.cpan.org/Public/Bug/Display.html?id=44495
>> http://rt.cpan.org/Public/Bug/Display.html?id=44038
>> http://rt.cpan.org/Public/Bug/Display.html?id=42970
>> are a bit discouraging. It also concerns me that the
>> module is based on svn 1.4, and we're running 1.6. I
>> will keep at it a bit longer though.
>>
>> I'm personally not against a simple bash shell approach,
>> but I'm following orders, so I will
>> continue researching modules.
>>
>> My list of updated list of candidates is here:
>> http://delicious.com/oynphwv/tmp-9fz
>>
>>> There's also an SVN:Look modules too:
>>> http://search.cpan.org/~gnustavo/SVN-Look-0.15/lib/SVN/Look.pm. The
>>> problem is that these particular Perl modules need access to a
>>> compiler, and the compiled Subversion API which is written in C.
>>
>> we're running Linux so I would expect gcc, and the gnu build toolset would
>> work
>>
>>> In many companies, you simply cannot use these Perl modules. This can be
>>> a big problem if you are distributing your Perl script for developers
>>> to use.
>>>
>>> However, the command line access in Perl via the "open" command works
>>> fine. The "svn" command has the option to produce XML output which
>>> makes parsing the output very simple. You can also use "system"
>>> commands or qx() to do things like "svn cp". The problem is that
>>> svnlook (which you'd use for hooks) doesn't produce XML output which
>>> makes it hard to parse.
>>
>> thanks for that perspective
>>
>> --snip
>>
>> --
>> regards,
>> Tom
>>
>
>
>
> --
> David Weintraub
> qazwart_at_gmail.com
>
> ------------------------------------------------------
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2423171
>
> Please start new threads on the <users_at_subversion.apache.org> mailing list.
> To subscribe to the new list, send an empty e-mail to <users-subscribe_at_subversion.apache.org>.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2423338
Please start new threads on the <users_at_subversion.apache.org> mailing list.
To subscribe to the new list, send an empty e-mail to <users-subscribe_at_subversion.apache.org>.
Received on 2009-11-23 14:14:57 CET