Re: dpkg modification: non-interactivity
>> "MB" == Mitch Blevins <mblevin@debian.org> writes:
MB> You have the much better:
MB> / -- <wait2>
MB> DOWNLOAD <wait1> CONFIGURE --|---- <wait2>
MB> \ -- <wait2>
MB> which avoids the multiple CONFIGURE stages on the individual machines.
MB> Is there a good way to reconcile the needs of these two types of users?
MB> For the second case, would it be best just to provide more/better tools
MB> that allow the admin to change the conffiles and/or installscripts
MB> within a .deb without having to get mired down in packaging details?
This would require, that the user makes the installationscript
non-interaktive.
He has to understand it and make the necessary changes. He may even
have to do some serious coding, if he want to provide different
answers to a question, depending on the machine the package installs
to.
This also won't address dpkg asking if it may overwrite a conffile.
Maybe some kind of expect script could be used.
Problem:
The packages have to be sorted, then extracted, and then, dpkg
--configure has to be called for each package in a specific order
(with the generated expect file), so the process won't stop because
packages A complains about package B not beeing fully installed
This requires a "master" workstation to do a sample install, so that a
proper expect script can be generated.
MB> (who is proud to now have posted 100% of the traffic to this list
MB> for the month of December)
Now you are down to 50 % :-)
Ciao,
Martin
Reply to: