Timothee Besset wrote:
> Garrett Rooney wrote:
>
>> Actually, I believe we decided not to move the perl bindings into a
>> separate project.
>>
>> That said, I would love to see some solution to the whole SVN::Core is
>> not on CPAN issue, as it is kind of irritating for people who are used
>> to installing perl modules via CPAN.pm or CPANPLUS.pm.
>>
> Well that would more or less mean compiling all of subversion from CPAN.
> Is that really adviseable? Or should a SVN::Core module ask for an
> installed subversion with source, and take care of building only the
> bindings part? Truth is, SVN::Core has more to SWIG and C++ than to perl ..
I don't know if it's advisable, but I've already gotten one email from a
CPAN tester complaining that SVN::Core couldn't be found, and I imagine
it's not a unique event. People expect to be able to install all the
dependencies of a module via CPAN, so it would be nice if we could
accomodate them.
That said, i'm not sure what the 'commonly done thing' is in situations
like this. I mean we can't be the first project with this kind of
problem...
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Mar 30 16:26:22 2004