Re: moving archdetect functionality to libd-i
On Tue, Jul 05, 2005 at 01:59:46AM +0200, Petter Reinholdtsen wrote:
> [Colin Watson]
> > Because then I have to create an archdetect.deb in addition to a
> > kbd-chooser.deb,
>
> Why would you need to create an archdetect.deb?
Because that's the only way I can get the archdetect program outside
d-i. The ddetect source package does not produce any other .debs. I
cannot cause the code to appear on the installed system by magic. :-)
> > and (given the individually small but cumulative cost of additional
> > packages) this seems wasteful to me when it could just as easily be
> > a library call. After all, the guts of archdetect are already
> > implemented in C, so when calling them from C one might as well not
> > have to go through another process.
>
> Is this to provide subarch detection in the installed system
Yes, but with the *specific* intent of being able to run code from d-i
in the installed system.
> in addition to the subarch detection available in d-i? If so, perhaps
> it would be OK with a standalone program to solve #238687?
There are two ways to fix that bug. Either:
* somebody duplicates all the code in archdetect somewhere else (seems
a bad idea);
* or we create something that is functionally equivalent to
archdetect.deb.
However, I think that *in any case* having an external program is less
good for the specific application I'm interested in (namely kbd-chooser)
than a library call. Note that libdebian-installer is already available
in .deb form.
Cheers,
--
Colin Watson [cjwatson@debian.org]
Reply to: