Julian Gilbey wrote: > A thread came up here a little while back about installation scripts > sometimes not being able to use debconf for security or other > reasons.
That's not particularly accurate. > But we would like an interference-free install. > > So what about introducing a dpkg-postconfigure program which runs > package.postconfig files after any dpkg run has finished, in an > analagous way to dpkg-preconfigure. Only this time, it will be only > for things that *must* wait till post-installation, and cannot use > debconf for whatever reason. There shouldn't be that many of these, > but it would probably be a good idea to introduce this soon as we move > to non-interactive installs. This is not necessary, it is perfectly possible to prompt for passwords or anything else in the postinst, using debconf, if you feel that is necessary for security reasons or whatever other reason. -- see shy jo
