[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: debian-installer main menu almost done



On Sat, Oct 28, 2000 at 05:40:27PM -0700, Joey Hess wrote:
> I'm happy to report that the main menu for the debian install 
> seems to be almost done. I have just two items on my TODO list:
>   * Fix the one warning at compile time.

--- tree.c      2000/10/28 22:58:30     1.6
+++ tree.c      2000/10/29 01:37:00
@@ -78,7 +78,7 @@
 #endif
 
 void _tree_free(void *nodep) {
-       struct package_t *p = (struct package_t **)nodep;
+       struct package_t *p = (struct package_t *)nodep;
 
        if (p->description)
                free(p->description);


Assuming _tree_Free is actually not segfaulting as written. You can get
rid of the cast entirely if you like, C will automatically convert to
and from a (void *).  (C++ won't)

>   * Figure out how to handle configuring only one virtual package (pick off
>     of a menu?) if the menu item depends on a virtual package.

I'm not quite sure how the details would work, but maybe you could make
a question for each dependency that can be satisfied by multiple udebs,
and just query that each time it's needed.

That'd make it awkward to have a virtual package provided by one udeb at
the start but by a different udeb later, maybe. (You wouldn't get asked
about it automatically, you'd have to go nonlinear or out of your way
or something) This may not matter.

Having looked at where d-i is upto, and how far it's got to go, I'm
inclined to think that aiming for d-i to be the installer for woody (for
all architectures, for all environments) isn't completely unreasonable.
We'll probably have to make a definite decision which one to go with
for woody by the end of November, though, to make sure we've got time
to hack on b-f if we need to.

Cheers,
aj

-- 
Anthony Towns <aj@humbug.org.au> <http://azure.humbug.org.au/~aj/>
I don't speak for anyone save myself. GPG signed mail preferred.

  ``We reject: kings, presidents, and voting.
                 We believe in: rough consensus and working code.''
                                      -- Dave Clark

Attachment: pgpNUQQyySBNw.pgp
Description: PGP signature


Reply to: