Re: Non-interactive install proposal
Andreas Degert <firstname.lastname@example.org> writes:
> Manoj Srivastava <email@example.com> writes:
> > Drake> On Tue, Jun 02, 1998 at 09:48:46PM -0500, Manoj Srivastava wrote:
> > >>
> > >> What is the benefit of keeping packages in an unconfigured
> > >> state?
> > Drake> It's a reminder to me that I need to configure this package still.
> > I prefer the approach to ask questions first, and configure as
> > it installs. If we are spending time to do this, we should do this
> > right.
> In general, you can't ask all questions first; you can ask some
> questions, then unpack and debian-configure the packages, but then you
> still have to do a lot of configuration (using an editor or some
> configuration programs that "ask questions").
A good way to start would be to seperate the unpacking and
installation from the configuration.
dpkg should start one thread to extract a package, when a package is
done a second threat is signaled and the next is extracted.
The second thread configures the package. If any question is to be
asked, the controll is given to a third threat and the next package is
The third thread pops up the question. As soon as the user has
answered the package is send back to the second thread to continue
installation. The third thread could search a database instead of
asking the user and only ask for unknown questions.
Now, if the user is tired of waiting and he goes of making coffee, the
installation will continue as far as possible and when he comes back
he has a bunch of questions to answere. The installation wouldn't
completly stop, just because on package want the user to press return
after reading some text (like a libc5 update does).
May the Source be with you.
To UNSUBSCRIBE, email to firstname.lastname@example.org
with a subject of "unsubscribe". Trouble? Contact email@example.com