-BEGIN PGP SIGNED MESSAGE-
As the official version of perl 5.004 is finally out (I must admit I
haven't installed the debian package yet, but I run webservers with lots
of perl CGI and can't afford to break them), I have a few questions,
comments, and thoughts.
1. In building my own
Hi,
Well, with 5.004, CGI-modules is obsolete, and so the
misnaming of the CGI modules package is a solved issue
;-). (Unless. of course, there is a hew-and-cry about removing the
package, I'd suggest removing CGI-modules from hamm).
As for the description issue, even the one
On 19 May 1997, Manoj Srivastava wrote:
Well, with 5.004, CGI-modules is obsolete, and so the
misnaming of the CGI modules package is a solved issue
;-). (Unless. of course, there is a hew-and-cry about removing the
package, I'd suggest removing CGI-modules from hamm).
No real
Scott K. Ellis [EMAIL PROTECTED] writes:
My main concern is that they neither bunch up on the dpkg select screen,
nor is it easy to search for perl modules in dselect (I'd like to be able
to find all the perl modules by searching on perl).
BTW, I maintain alias and www-search (and libwww-perl
-BEGIN PGP SIGNED MESSAGE-
Scott Ellis, in an immanent manifestation of deity, wrote:
As the official version of perl 5.004 is finally out (I must admit I
haven't installed the debian package yet, but I run webservers with lots
of perl CGI and can't afford to break them), I have a few
this since he asked for it a while back. The upgrade to libc6 for perl
can't happen until there is a libgdbm compatible with it though since I
refuse to break everyone's dbm interfaces. I'll also be able to release
Great - as soon as I get some consensus on package naming, I'll try to
put
6 matches
Mail list logo
