Re: patch to fix debootstrap invocation on local archive
[ Sorry to come in late. ]`
Adam Di Carlo wrote:
> > * failures/success (duh)
>
> Yes, with some well defined exit codes so we can take appropriate
> action in dbootstrap if possible.
Yes.
> > * progress -- how much has downloaded (x%), what's happening
> > (I: installing essential packages), etc
>
> I'm not sure yet. I would guess a nice little % bar with an area
> beneath it showing what it's currently doing ...
>
> > * interactivity -- "please insert the 5th base-system floppy"
> >
> > I'm happy to do just about anything on the debootstrap end for this;
> > what's convenient for boot-floppies? Calling a program, displaying the
> > slang stuff "myself", using a named pipe, using stdio?
>
> Probably using the slang stuff. Are you internationalized? We will
> probably end up linking all slang stuff with the slang-wide libs
> (IIRC).
>
> We need to think of using this for both boot-floppies and
> debian-installer. However, we don't include debconf on the root
> filesystem. I would imagine a straight slang interface is best.
For debian-installer, I would much prefer if the data and its
presentation are kept seperate. So debootstrap could output something
that contains the info we need, and is also informative standalone:
1% downloading blah
5% downloading meh
7% downloading foo
10% downloading really_large_thing
50% bootstrapping dpkg
60% installing meh
70% installing foo
80% installing blah
90% cleaning up
100% done!
This is trivial to parse, so the boot floppies can parse it and display
a status display just like Adam wants. Likewise, a trivial program can
contert it into the debconf protocol, using the gauge data type (which I
just proposed on the debconf mailing list), and display it using
cdebconf with whatever frontend debian-installer is using.
You might want to prefix the lines with some flag like "status: " or
something, if there is lots of random other text being output by
debootstrap and the programs it runs.
> I would also suggest, if possible, different verbosity. We have
> 'debug' (does more syslogging), and orgthagonal to that, verbose,
> normal, and quiet modes. We can pass this to you as a switch,
> probably either a -q or a -v switch.
Hmm, you're thinking about different verbosity levels for the progress
text itself? I suppose it would be very handy to get all the output of
the debootstrap run in debug mode, but I'm not sure if it fits in with
my idea very well.
--
see shy jo
Reply to: