Installed debconf 0.1.35 (all source)
Installed:
debconf_0.1.35.tar.gz
to dists/potato/main/source/admin/debconf_0.1.35.tar.gz
replacing debconf_0.1.34.tar.gz
debconf_0.1.35.dsc
to dists/potato/main/source/admin/debconf_0.1.35.dsc
replacing debconf_0.1.34.dsc
debconf_0.1.35_all.deb
to dists/potato/main/binary-all/admin/debconf_0.1.35.deb
replacing debconf_0.1.34.deb
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.6
Date: Thu, 23 Sep 1999 12:52:14 -0700
Source: debconf
Binary: debconf
Architecture: source all
Version: 0.1.35
Distribution: unstable
Urgency: low
Maintainer: Joey Hess <joeyh@master.debian.org>
Description:
debconf - Debian configuration management system
Changes:
debconf (0.1.35) unstable; urgency=low
.
* Mappings. What good are they? None, that I could see, so I completely
removed them! This doesn't influence debconf's behavior at all, just
removes many lines of code and makes it all easier to understand.
* Added the concept that each question is owned by one or more packages.
When the number of owners goes to zero, the question is removed.
* Whenever a question is removed, I check to see if the template it used
is no longer used as well. If so, it's also removed.
* What this lets us do is it allows packages to get rid of questions and
templates they created when they are purged. And shared questions are
fully supported and won't go away until the last package that uses them
does.
* Added a "purge" command that accomplishes this easily. (You could of
course always call unregister by hand for each question, but this is
easier.)
* Modifed dpkg-preconfig so all the templates in all the packages that
are being installed are read first, and then all the config scripts are
run.
* The changes above have an intriguing side benefit that offers a fix to a
vexing problem. There is now a field in each question called "owners", that
is a comma and space delimited list of the packages that have registered
ownership. This list is up to date as soon as all the templates are
loaded if apt is used. A set of related packages can all provide the same
template in them; and their config scripts can then look at the owners
field to get the list of all related packages that is/will be installed.
Then they can do things like turn that into a list of choices of window
managers, or ispell dictionaries, etc, and prompt the user to pick one.
This feels only a little hackish, and the only problem with it is that if
they are not installing with apt, the list isn't fully complete until each
and every package has been installed.
* Fixed question default value code so it always inherits from the current
template, whatever that might be.
Files:
4e1ab4a165bdb68a4aa83665c7cc22b8 491 admin optional debconf_0.1.35.dsc
02364266a4cfaf82a832da7d6477b780 59538 admin optional debconf_0.1.35.tar.gz
4f3ecc54c0354dd6565151c821241391 63564 admin optional debconf_0.1.35_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.0 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE369tj2tp5zXiKP0wRAhxAAJ9f29SDjGQG5w9EQVjU6t/FzwE7DwCeIDkk
VmDfC8S69F9pFrVKJMQslQc=
=VPA7
-----END PGP SIGNATURE-----
Reply to: