Re: Using linuxconf
On Sun, 27 Oct 1996, Bernd Eckenfels wrote:
> > change the underlying system overnight and everything breaks until
> > it's been changed to work with the new system. A package would have
> > to use the new system immediately.
>
> Aehm.. no. If you dont change a pacage to use getconf/configtoll you
> imply cant configure that package with linuxconf. But you can still
> use it. Don't see any problem with it.
no, that's not what i'm implying at all.
what i'm directly stating is that, according to the linuxconf docs, it
takes control of the system at a very early stage and *replaces* the
existing boot scripts.
Since many packages are dependant on the current boot scripts, they will
break as soon as linuxconf is installed unless they are patched to work
with linuxconf.
> a) move all packages to new configuration style
> b) port linuxconf to understand new configstyle (and things like /etc/passwd
> and stuff)
>
> -> you can configure more and more with linuxconf without breaking anyhing
> (you can still use the old configscripts for old packages).
yes, if switching to linuxconf can be done gradually without breaking
anything then i'm all for it. From what I know of linuxconf at the
moment (admittedly I am *not* an expert on it), that is not at all
likely.
if, however, linuxconf is patched so that it works seamlessly with
debian then that will be no problem at all.
And that's my point - it's up to whoever takes on the job of packaging
linuxconf for debian to ensure that it doesn't break existing packages.
Craig
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-REQUEST@lists.debian.org . Trouble? e-mail to Bruce@Pixar.com
Reply to: