Re: Debian Perl Modules
I just downloaded perl 5.6.0 which was released yesterday, and I did
a
$ ./configure.gnu --prefix=/usr/local
and it looks if all is well. I ran dselect, and it looks as if it still
works. I also checked to make sure that my original perl 5.005_03 is
still in /usr/bin and it looks as if it is there too. So, all looks good,
and it appears that I can successfully maintain two different versions
of perl, on that supports my debian, and one that I can use to implement
bleeding edge features.
brian
On Fri, Mar 24, 2000 at 08:51:53AM -0800, Brian Lavender wrote:
> I still have a question regarding the debian perl modules. It appears that
> dpkg and apt have perl modules. If I went in and replace perl with a newer
> version from source, I would have to rebuild those modules. If I look at
> my libraries of my Potatoe installation I see some Debian perl modules.
> You see there is a DebianNet.pm and a Debian directory. Did these perl
> modules come out of the dpkg and apt debian packages? I am thinking
> about replacing the perl with my source version. If I want to do that
> and have it replace the debian version, I am going to have to make sure
> that those modules exist. Where would I get these debian perl modules? I
> don't see them on CPAN or in the debian source tree. Of course maybe I
> did not look thoroughly.
>
> I think I do see a point where I could install a new version of perl in
> /usr/local and have that version co-exist with the perl supporting my
> Debian system.
>
> $ ls -F /usr/lib/perl5
>
> 5.004/
> 5.005/
> 5.00503/
> Bundle/
> Data/
> Date/
> Debian/
> DebianNet.pm
> Dpkg/
> File/
> HTML/
> HTTP/
> I18N/
> LWP/
> LWP.pm
> Mail/
> Net/
> SGMLS/
> SGMLS.pm
> Text/
> Time/
> URI/
> URI.pm
> WWW/
> auto/
> dialog.pl
> i386-linux/
> lwpcook.pod
> sgmlspl-specs/
> site_perl/
>
>
> $ ls -F /usr/lib/perl5/Debian
>
> DebConf/
> DpkgFtp.pm
>
> $ ls -F /usr/lib/perl5/Dpkg
>
> Archive/
> Package/
>
> On Fri, Mar 24, 2000 at 01:40:36PM +1030, John Pearson wrote:
> > On Thu, Mar 23, 2000 at 10:10:00AM -0800, Brian Lavender wrote
> > > I was taking a look at the perl modules on my debian system, and I
> > > noticed that there are a couple of Debian perl modules. In fact I
> > > once built a newer version of perl on my debian system, and I noticed
> > > that apt, and I believe dpkg stopped working.
> > >
> > > My Question:
> > > Is it possible to build a new version of perl on my debian system and
> > > install these perl modules? Say I have slink I want to upgrade perl to
> > > the latest. Can I add in these perl modules, and where would I get the
> > > source to add them?
> > >
> >
> > Slink perl uses a different layout for /usr/lib/perl5 to
> > that used for later perls; it changed for Potato, I'm guessing
> > to allow multiple perl versions to co-exist; slink perl has
> > directories like
> > /usr/lib/perl5/i386-linux/5.004/auto/
> > /usr/lib/perl5/i386-linux/5.004/CORE/
> > and so on, whereas perl5 from potato uses
> > /usr/lib/perl5/5.005/i386-linux/auto/
> >
> > I seem to recall that both layouts differ from the
> > default specified in the perl distribution.
> >
> > As a result, slink packages that insert files in /usr/lib/perl5
> > are not compatible with later perl packages.
> >
> > Your options appear to be:
> > - Stick to slink perl & related packages;
> > - Build the version of perl that you want, but ensure that
> > it uses the 'slink' directory conventions; you may also
> > have to rebuild perl-dependent packages if the changes to
> > perl break them in other ways;
> > - Upgrade to potato (or at least, upgrade perl & related packages)
> > and be happy with the perl versions that provides;
> > - Upgrade at least perl & related packages to potato and
> > then build the perl of your choosing using the potato
> > conventions or installing into /usr/local/, without replacing
> > the potato perl that other packages rely on.
> >
> > If you haven't actually replaced the slink version of perl
> > (i.e., you simply installed the new perl alongside of the old
> > one, either in /usr/local/ or replacing /usr/bin/perl) then
> > you may be able to have the two coexist peacefully by renaming
> > your new perl binary to (e.g.) 'perl-local' and (if necessary)
> > replacing /usr/bin/perl by hand from the slink package; it
> > depends if your new perl clobbered files from the slink perl.
> >
> > HTH,
> >
> >
> > John P.
> > --
> > huiac@camtech.net.au
> > john@huiac.apana.org.au
> > "Oh - I - you know - my job is to fear everything." - Bill Gates in Denmark
> >
> >
> > --
> > Unsubscribe? mail -s unsubscribe debian-user-request@lists.debian.org < /dev/null
>
> --
> Brian Lavender
> http://www.brie.com/brian/
>
>
> --
> Unsubscribe? mail -s unsubscribe debian-user-request@lists.debian.org < /dev/null
--
Brian Lavender
http://www.brie.com/brian/
Reply to: