Installed debconf 0.4.00 (all source i386)
Installed:
debconf_0.4.00.dsc
to dists/woody/main/source/admin/debconf_0.4.00.dsc
replacing debconf_0.3.83.dsc
debconf_0.4.00_i386.deb
to dists/woody/main/binary-i386/admin/debconf_0.4.00.deb
replacing debconf_0.3.83.deb
debconf-doc_0.4.00_all.deb
to dists/woody/main/binary-all/admin/debconf-doc_0.4.00.deb
replacing debconf-doc_0.3.83.deb
debconf_0.4.00.tar.gz
to dists/woody/main/source/admin/debconf_0.4.00.tar.gz
replacing debconf_0.3.83.tar.gz
debconf-utils_0.4.00_all.deb
to dists/woody/main/binary-all/devel/debconf-utils_0.4.00.deb
replacing debconf-utils_0.3.83.deb
-----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: source all i386
Version: 0.4.00
Distribution: unstable
Urgency: low
Maintainer: Joey Hess <joeyh@debian.org>
Description:
debconf - Debian configuration management system
debconf-doc - Debian configuration management system documentation
debconf-utils - Debconf utilities
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:
98c62e1c975540cc234ba574bda86965 731 admin standard debconf_0.4.00.dsc
552babc3a9e6cb24cb086fae493e3b72 211672 admin standard debconf_0.4.00.tar.gz
11775342c27f341caca3cfa7d0aee63b 111156 admin standard debconf-doc_0.4.00_all.deb
72d22ee555e2222a756ffb204362da12 46504 admin standard debconf-utils_0.4.00_all.deb
bbfdf9828231e1d482ef0d4e957d7903 71160 admin standard debconf_0.4.00_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.3 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE57WWN2tp5zXiKP0wRAu/yAKCi5LVRDQWGatfRxsX3B7FXeleBnQCgkUvB
ELluGo5nryhLeKFLk9z0Dp8=
=1xg5
-----END PGP SIGNATURE-----
Reply to: