-----BEGIN PGP SIGNED MESSAGE----- Raphael Hertzog, in an immanent manifestation of deity, wrote: >Le Wed, Jul 07, 1999 at 07:20:33PM +0200, Piotr Roszatycki écrivait: >> Should I prepare libcgi-pm-perl package with new CGI.pm file? Or >> put new CGI.pm to my libapache-asp-perl (it will overwrite file from >> perl-5.005)? > >I vote for updating the modules contained in the perl-5.005 package.
So, I would release a new perl-5.005 package when a new CGI.pm was released? This doesn't sound real feasible to me. Why wouldn't a new libcgi-pm-perl package be released, it can just divert or replaces parts of the package as it needs to. So, is there anything that can be done about libcgi-perl = CGI-Modules? Darren - -- <[EMAIL PROTECTED]> <http://www.daft.com/~torin> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Darren Stalder/2608 Second Ave, @282/Seattle, WA 98121-1212/USA/+1-800-921-4996 @ Sysadmin, webweaver, postmaster for hire. C/Perl/CGI/Pilot programmer/tutor @ @ Make a little hot-tub in your soul. @ -----BEGIN PGP SIGNATURE----- Version: 2.6.3a Charset: noconv Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface iQCVAwUBN4P/MrQuaHP6LBjxAQGSrAP9Gobc3/Igd75vLN3q2wc4AvPq+/3y7uy/ b81Yijsn/1phBoNp0G77kh+ZGCsRwZHjdjpxn+RXjx1Vf4RawUXF9rVf+MD0IgTe 9oUbISpnFzKCE1vKmCqzewg28pNYWOxg8Q61Sb/r+ms9CpyRFeyMqRDJ2QthOcwk 61saAbkBP20= =9Cpb -----END PGP SIGNATURE-----
