Uploaded debconf 0.4.00 (m68k) to erlangen
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.6
Date: Tue, 17 Oct 2000 13:35:41 -0700
Source: debconf
Binary: debconf-utils debconf debconf-doc
Architecture: m68k
Version: 0.4.00
Distribution: unstable
Urgency: low
Maintainer: Debian/m68k Build Daemon <buildd@kullervo.informatik.uni-erlangen.de>
Description:
debconf - Debian configuration management system
Changes:
debconf (0.4.00) unstable; urgency=low
.
* Removed recursive build-dependancy on debconf-utils. There were two
ways to do this, the quick hack way and the move lots of directories in
cvs way. I took the latter.
* While I was reorganizing *EVERYTHING*, I renamed all the perl modules,
what was Debian::DebConf::foo is now Debconf::foo.
Debian::DebConf::Client::ConfModule is now just Debconf::ConfModule, but
a stub module exists in the old location for backwards compatability
(thanks, bod).
* If you use the new module, you should depend on this version of
Debconf!
* This hacking also required some ugly ugly hacking of the debconf
database. Debconf needs a real database. :-(
* I guess this means the filename in all the .po files are wrong, bug
since those filenames are in comments, the .po files should continue to
work, right?
* debconf-utils now depends on debconf >= 0.4, so it will continue to
work.
* Needless to say, this was a massive PITA all around. I've NEVER going
to do this again, so I hope I got it right.
* For a short while, I considered using MakeMaker. That is, until I
noticed MakeMaker had no way of marking scripts for install into
/usr/sbin, and after not one but two perl gods advised me using it for
anything more cpmplex than a simple library package was not a good
idea. People have asked me to use MakeMaker in the past, and it's just
not going to happen unless you send me a very nice patch.
Files:
5de21a6370581b1c8394251e44b61343 70394 admin standard debconf_0.4.00_m68k.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.5 and Gnu Privacy Guard <http://www.gnupg.org/>
iEYEARECAAYFAjnwROQACgkQcS3JWD3Fdve9wQCfacnP+8i2w6xOn3ku0moCw5/F
fpIAn32UAk0qyGLLkg2+JG9Nx5EvRBQf
=w9w2
-----END PGP SIGNATURE-----
Reply to: