mån 2003-03-17 klockan 19.18 skrev Denis Barbier: > > 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. Are they? db_subst foo/bar NAME "..." Will that be gobbled? > > > 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? But debconfclient.h isn't necessary for *running* a C program that uses the C interface. Policy dictates a split in runtime package and devel package, doesn't it? Do we really want to stick a shared library in the debconf package? What about when the soname changes? I just don't see what the problem is with having libdebconfX and libdebconfX-dev packages. /M -- Martin Sjögren sjogren@debian.org -- marvin@dum.chalmers.se GPG key: http://www.mdstud.chalmers.se/~md9ms/gpg.html let hello = "hello" : hello in putStr (unlines hello)
Attachment:
signature.asc
Description: Detta =?ISO-8859-1?Q?=E4r?= en digitalt signerad meddelandedel