Mail Archives: djgpp/2003/03/29/04:52:30
Hello.
Andrew Cottrell wrote:
>
> >> > > I've got some more time to look into perl and I've downloaded Perl
> >> > > 5.8.0 over Perl 5.6.1. I ran the command from bash
> ..SNIP..
> >Andrew: Is Pod/ParseLink.pm in the Perl 5.8.0 binary package on clio.rice.edu?
> >How did you generate the binary distribution?
> The last Perl 5.8.0 I built was on 3-Dec-2002. I would have used the
> Perl 5.6.1 manifest files to generate the zip file.
Oh. I don't think that approach will work. Perl 5.8.0 comes with a lot more
modules, e.g.: some new IO::* classes. It looks like the Unicode support is
pretty different as well.
Maybe we should just remove the package or mark it as deprecated or
"dangerous", until it's been ported?
> >When I generated the Perl 5.6.1 binary package, I had to hack the install
> >scripts, to install into my temporary package-creation area. Did you do
> >something similar? Or did you install into $DJDIR and then tar up the relevant
> >files? Does Perl generate a manifest file on installation?
> I don't remember haveing to do any hacking (but I may be wrong as this
> was done last Oct/Nov).
> The Perl 5.8.0 binary file at clio includes the manifest files. Perl
> built from the FSF source tarball without any problems as far as I
> could see, but since the origianl build you have patched Perl 5.6.1
> and there were reports of problems with the Perl 5.8.0 last year
> regarding help docs and some other quirks. Instead of spending allot
> of time on updating Perl 5.8.0 and due to work comittments I now only
> build Perl 5.6.1.
I keep meaning to look at porting 5.8.0. But there's just not enough time in
the day. ;)
Thanks, bye, Rich =]
--
Richard Dawe [ http://www.phekda.freeserve.co.uk/richdawe/ ]
- Raw text -