On 20 April 2011 03:30, Alex Mestiashvili
wrote:
> On 04/20/2011 05:55 AM, Jim Green wrote:
>>
>> Hello!
>> in squeeze most perl modules are not up-to-date. for example
>> libmoose-perl.
>>
>> In this case I include the sid repo and attempt to upgrade to sid
>> version of libmoose but a hell of de
2011/4/20 Jim Green
> Hello!
> what should be the best practice here right now? I use cpan command to
> install some modules that are not available in debian. but how about
> those not up-to-date ones?
>
What about using locallib+cpan or a chrooted+(cpan|sid) enviromment for your
perl applicatio
On 04/20/2011 05:55 AM, Jim Green wrote:
Hello!
in squeeze most perl modules are not up-to-date. for example libmoose-perl.
In this case I include the sid repo and attempt to upgrade to sid
version of libmoose but a hell of dependency begins. I am afraid if
insist on upgrading this module, lots
little more work, but a lot of people will benefit from it.
For development and testing I tend to have a local CPAN installation
directory ~/perl5. CPAN can be tweaked to install all it's modules in
that users home directory, if run with that user.
Then I do not need to have root privileg
Hello!
in squeeze most perl modules are not up-to-date. for example libmoose-perl.
In this case I include the sid repo and attempt to upgrade to sid
version of libmoose but a hell of dependency begins. I am afraid if
insist on upgrading this module, lots of perl core module/perl would be
upgraded
Quick question - Where is the best directory to locate the modules to? I have
the CPAN library on CD and would like a pointer on where to put them.
--
-= Sent by Debian 1.3 Linux =-
Thomas Kocourek KD4CIK
@[EMAIL PROTECTED]@westgac3.dragon.com Remove @_@ for correct Email address
--... ...-- ..
Hi,
Count me in. I used to maintain the CGI modules, so I have
some experience there ;-). My only concern is the amount of time I
have, but I'll be glad to help where I can.
manoj
--
"If we fail to draw the line in Vietnam we may find ourselves
compelled to draw a defense lin
"Brian S. Julin" <[EMAIL PROTECTED]> writes:
[snip]
> So all we would need to do is write our own version of MakeMaker that,
> in addition to the usual targets like "test" "dist" and "install", also
> automatically created rules for construction of a "deb" and "dsc"
> target.
We'd really just
Brian S. Julin wrote:
> So all we would need to do is write our own version of MakeMaker that,
> in addition to the usual targets like "test" "dist" and "install", also
> automatically created rules for construction of a "deb" and "dsc"
> target.
This is a really cool idea.
One concern is th
Greetings fellow Debianites,
Those of you who program in perl probably have a bunch
of perl module source trees in /usr/src which you installed
yourself. Although Debian developers have packaged the most
essential of the Perl modules (the CGI ones, basically), with
a couple hundred modules on
10 matches
Mail list logo
