On Mon, Mar 17, 2003 at 06:51:49PM +0100, Martin Sjögren wrote: > mån 2003-03-17 klockan 14.55 skrev Denis Barbier: > > > The fix is probably simple, move the argument splitting from confmodule > > > to the individual commands. > > > > Then the debconf protocol should specify when spaces are significant and > > when they are not. > > I would think it obvious that they would be significant inside the > strings I want to substitute in.
But this is not always possible, consider the shell confmodule for instance, spaces between arguments are gobbled by the shell. > > > Maybe we should do some thinking and decide exactly which header files > > > need to be in the -dev package. debconfclient.h obviously. frontend.h > > > and whatever the frontends need? Damn, looking at text.c that's a lot. > > > :( > > > > > > But I don't see why confmodule.h and commands.h need to be there. > > > > But is there a need for -dev at all? debconfclient.[ch] should go into > > debconf, these files define a C interface similar to current Perl, Python > > or shell ones. Other .h files are useless, aren't they? > > debconf or cdebconf? debconf. The debconfclient.[ch] files are similar to /usr/share/debconf/confmodule, /usr/share/perl5/Debconf/Client/ConfModule.pm and /usr/lib/python2.2/site-packages/debconf.py Perl, python and shell confmodule's are shipped by debconf, so why not C? > I think it's quite reasonable to have a libdebconf1-dev for the > libdebconf1 package (which is still needed, no matter whether you've > got debconf or cdebconf installed). This may be obvious, but why is it needed? Only cdebconf uses it. > Perhaps it's an idea to split libdebconf in libdebconfclient and > libcdebconf? (note the c, since that package would only be used > together with cdebconf, to write frontends perhaps). Denis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
