Raphael Hertzog <[EMAIL PROTECTED]> writes: > Le Thu, Nov 18, 1999 at 12:55:46PM +0100, Stephane Bortzmeyer écrivait: > > > A script with "use POSIX" will fail. > > > > OK, it means POSIX is not in perl-base. > > No, POSIX is in perl-5.005-base. But some files (autosplit.ix at least) > are missing.
That definately sounds like a bug, and exactly the sort of thing I'm worried about. This bug is filed, Bug#50242. > > * Is it a problem? For who? > > POSIX is needed for the i18n of perl script from the base system (adduser > comes to my mind) Yup. Adduser had to take out some stuff. If moving more of POSIX to base is an issue (i.e., it's very large) then we need to get in touch with Wichert on what part of POSIX he was lacking. I believe if was something like POSIX errors. > > Again, is it a bug? It's a problem for debconf, sure (even the tiny > > version uses Data::Dumper) but for who else? > > Well, debconf will go in base so the Data::Dumper module must go in base. > > > Should I fill in a bug against perl-5.005-base asking for POSIX and > > Data::Dumper? I thought the data::dumper or other debconf-base module requeses *were* filed as a bug... Damn... Well, it should be... > If such a bug is not yet filled yes. And explain to Darren, that they > should be corrected rapidly in order to let people test further > the new boot floppies. I can NMU the perl packages in order to correct > this if Darren can't do it ... Darren says he's back and actively working on things. I've cc'd debian-perl. Again, my concern is that the bugs *are* filed so maintainers are aware. My goal is that we can sort this stuff out over the next 2-3 weeks, and have a really robust base by that point. As for how far the perl-5.005-base testing, at the most extreme testing, we would try little scripts testing every module shipping to make sure they work (i.e., doesn't depend on stuff not shipping with perl). As for testing base in general, my main concern is that all the commands work as expected... -- .....Adam Di [EMAIL PROTECTED]<URL:http://www.onShore.com/>