From: Jakub Narebski <jnareb@gmail.com>
To: Georg-Johann Lay <avr@gjlay.de>
Cc: Christian Couder <christian.couder@gmail.com>, git@vger.kernel.org
Subject: Re: subversion-perl missing
Date: Mon, 26 Sep 2011 10:17:04 -0700 (PDT) [thread overview]
Message-ID: <m3k48vp6l7.fsf@localhost.localdomain> (raw)
In-Reply-To: <4E80AD1B.3080700@gjlay.de>
Georg-Johann Lay writes:
> Christian Couder schrieb:
> > On Mon, Sep 26, 2011 at 1:48 PM, Georg-Johann Lay <spam@spam.com> wrote:
> > > Where do I have to go to get the svn+perl stuff? Couldn't locate anything like
> > > that in subversion.tigris.org, so that I am stuck and need some hints on how to
> > > proceed.
> >
> > Perhaps you can try to install this module from CPAN:
> >
> > http://search.cpan.org/~mschwern/Alien-SVN-v1.6.12.1/
> >
> > or from it's github repo:
> >
> > https://github.com/schwern/alien-svn
>
> Hi Christian,
>
> thanks for that hint.
>
> After getting that piece of software, running ./Build.PL and ./Build I just
> don't know what to do next. The README doesn't say anything about how to use
> the built modules or how to do an install.
If you don't have admin privileges on the box, the best solution would
be to use local::lib[1] to install Perl modules in your home directory
for you (#perl IRC channel on FreeNode, or perlmonks are really helpful).
I really recommend it, together with cpanm[2] (which can configure
local::lib for you, via --local-lib option), though the latter is not
necessary.
[1]: http://search.cpan.org/~apeiron/local-lib-1.008004/lib/local/lib.pm
[2]: http://search.cpan.org/~miyagawa/App-cpanminus-1.4008/bin/cpanm
If you have admin privileges, I think the best solution would be
either find repository which has subversion-perl that matches your
version of Subversion, or compile subversion-perl from a source
package... though this might be more difficult, it has advantage of
being in package management.
> As git-svn complains
>
> ...Can't locate SVN/Core.pm in @INC (@INC contains: ...
>
> and
>
> schwern-alien-svn-9298884>find . -name 'Core.pm'
> ./src/subversion/subversion/bindings/swig/perl/native/Core.pm
> ./src/subversion/subversion/bindings/swig/perl/native/blib/lib/SVN/Core.pm
>
> the question is how to do the final trick of telling git how to use Core.pm
> (and which of the two?) and do the connexion between git and alien-svn.
>
> Sorry for the noob questions, never used perl or git before...
You have to install subversion-perl somewhere, not only build it.
Though you could fiddle with PERL5LIB (which is PATH-like environmtne
variable to specify where to search for Perl modules) to make Perl
find your built but not installed Alien::SVN.
HTH
--
Jakub Narębski
next prev parent reply other threads:[~2011-09-26 17:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 11:48 subversion-perl missing Georg-Johann Lay
2011-09-26 13:03 ` Michael J Gruber
2011-09-26 13:41 ` Georg-Johann Lay
2011-09-26 14:18 ` Michael J Gruber
2011-09-26 14:51 ` Georg-Johann Lay
2011-09-26 14:54 ` Michael J Gruber
2011-09-26 21:11 ` Andreas Schwab
2011-09-26 14:48 ` Christian Couder
2011-09-26 16:49 ` Georg-Johann Lay
2011-09-26 17:17 ` Jakub Narebski [this message]
2011-09-28 10:06 ` Georg-Johann Lay
2011-09-28 12:59 ` Jakub Narebski
2011-09-28 15:54 ` Georg-Johann Lay
2011-11-29 15:39 ` Jason
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3k48vp6l7.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=avr@gjlay.de \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.