On Sun, 20 Apr 2003 21:48:48 +0300, Jarno Elonen <[EMAIL PROTECTED]> said:
>> ucf still has the same fundamental problem with regard to
>> preconfiguration, which was the primary issue that I raised in my
>> original message. The consensus, as I recall, was that
>> preconfiguration is important, and that prompting in postinst
>> should be minimized.
> I may have missed something but why can't the changed/merged
> configuration files be saved somewhere in preinstall phase and the
> current "live" configs be overwritten only in the postinstall phase
> by dpkg or postinst scripts if the rest of the installation went
> well?
Well, for configuration files that require the unpacked
package to generate, you can't ask during preconfiguration. For files
created using non essential packages, you need to wait until
postinst, or else those utilities may not be available.
Thus, in a number of cases, the ``new'' configuration file is
not determinable in the preinst phase.
Even for files in the package there is no way for ucf to get
at them -- especially given that the files handled by ucf are not
conffiles, and thus mingled in the package data.
manoj
--
Virtue is a relative term. Spock, "Friday's Child", stardate 3499.1
Manoj Srivastava <[EMAIL PROTECTED]> <http://www.debian.org/%7Esrivasta/>
1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
