alexander.hartmaier at t-systems
Oct 28, 2009, 10:37 AM
Post #33 of 38
(719 views)
Permalink
|
Is building a package for every perl module (not only cpan, private too)
really of help and not just a waste of time?
I'm using debian as server os since version 3 for running apps using POE
and webapps using Embperl and Catalyst and never managed to break it.
And yes I update almost every module by a script using cpanplus
excluding just some like mod_perl and Net::SNMP regularly.
--
best regards, Alex
Am Mittwoch, den 28.10.2009, 18:15 +0100 schrieb John Lee:
> Paul Makepeace wrote:
> > I recently have completely tossed using Debian's perl packages
> > because, while I do love Debian and all its package awesomeness, there
> > simply wasn't the package lib*-perl support in stable/lenny and even
> > testing/squeeze didn't have all the goods needed for a (what I think
> > is) fairly regular Catalyst install.
>
> ++ here. I had to build a lot of missing modules, or upgrade modules,
> that we wanted / needed. I actually didn't mind the headaches of
> chasing down dependencies when building my own packages using
> dh-make-perl, because it made it so much simpler system-side to
> distribute libraries (with dependencies!) with apt-get installs.
>
> The roadblock came when the packaged perl libraries needed to be
> upgraded in a manner inconsistent with the platform. For example,
> running perl 5.8.8 in an Ubuntu LTS installation, when you wanted
> features found in perl 5.10.0. When I started getting blocked on
> upgrades due to conflicts with, say, perl-base and perl-modules, or
> requirements for libperl5.10, I scrapped it and went with a source-built
> perl and CPAN. I even went through the process of creating updated
> perl, perl-base, and perl-module packages based on 5.10, but eventually,
> systems dependencies on the old version catch up to you.
>
> > So my question then is: given you've presumably done this, which of
> > your quoted solutions do you like best? I tried dh-make-perl many
> > moons ago and gave up due to annoyances around following dependencies.
> > Maybe CPP::Dist::Deb or something else solves that.
>
> I didn't give CPP a try, but I had a lot of experience with
> dh-make-perl. I found that it gave you a good start, but you have to be
> anal about creating packages for dependencies and setting descriptions.
>
> > I'm hoping local::lib + cpan + git solves this but curious how
> > Debian-integrated solutions work too.
>
> I'd be curious to see if this works well for folks too! I'm especially
> interested in folks who do this with a perl installed to a separate
> location, e.g. /usr/local/bin/perl. I worry about things like C library
> dependencies (ImageMagick comes to mind).
>
>
> - John
>
>
> _______________________________________________
> List: Catalyst[at]lists.scsys.co.uk
> Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
> Searchable archive: http://www.mail-archive.com/catalyst[at]lists.scsys.co.uk/
> Dev site: http://dev.catalyst.perl.org/
*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*
T-Systems Austria GesmbH Rennweg 97-99, 1030 Wien
Handelsgericht Wien, FN 79340b
*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*
Notice: This e-mail contains information that is confidential and may be privileged.
If you are not the intended recipient, please notify the sender and then
delete this e-mail immediately.
*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*"*
_______________________________________________
List: Catalyst[at]lists.scsys.co.uk
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst[at]lists.scsys.co.uk/
Dev site: http://dev.catalyst.perl.org/
|
