On Mon, Oct 02, 2000 at 10:18:30PM -0700, Randolph Chung wrote:
> Here's a bit of code that doesn't do anything useful yet, but illustrate
> some ideas about how a C-implementation of debconf may be built:
> http://auric.debian.org/~tausq/cdebconf-0.10.tgz
Well, at first glance it looks pretty good to me. It seems to segfault
pretty readily, but otherwise seems much more advanced than I expected.
> frontend {
> default {
> driver "ncurses"; // use the ncurses frontend by default
> };
>
> driver "ncurses" {module "modules/frontend/ncurses.so";};
> driver "text" {module "modules/frontend/text.so"};
> };
It might be better to have the drivers autodetected based on what's in the
filesystem, rather than using a config file. That way each frontend can
have its own udeb and no one has to worry about messing with configuration
files from postinsts.
> database {
> default {
> driver "textdb"; // use the textdb database backend by default
> };
> driver "textdb" {module "modules/db/textdb.so";};
> };
> if anything looks odd, it's because i wrote most of it on a plane :-)
> seriously though, comments/suggestions are most welcome. volunteers to
> work on this will be very much appreciated too!
So running ./debconf /var/lib/dpkg/info/netbase.config segfaults on my
part way through, but I'm not sure if that's just because I'm not running
it in the right environment or because of bugs, or what.
A better TODO list might be helpful. Or is there nothing more to do
(except maybe fix some bugs and add other frontends)?
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:
pgpwWHaQUP8E8.pgp
Description: PGP signature