[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: "dselect" replacement team

On Fri, 11 Apr 1997, Tom Lees wrote:

> On Fri, 11 Apr 1997, Wichert Akkerman wrote:
> > Maybe we should split the dselect effort into two groups: one group to
> > design and implement a library with an simple elegant API to interface
> > with the dpkg-libraries. This should start with a C-library and could
> > later be extended with a C++-wrapper. The second group should work on
> > the interface. Using this method it is possible to start with adapting
> > the current dpkg-code to the new API. Changes (or new implementations) of
> > the library code can then be used as drop-in replacements so no changes
> > to the user interface is necessary.
> Good idea, but since the UI can literally not be written until the library
> has been, not very practical. Maybe a better idea would be to extend the
> group after the initial library code has been written, so the original
> group writing the library is 6, then is is increased to 9, of which 3
> (from the original crowd) maintain the library, and 6 write the
> user-interface.

The library that dselect needs to begin to function is thankfully pretty
simple, so it can be pounded out in about a week or less. After that they
would hopefully be totally separate, functions being added to the library
as new needs are discovered, etc..

Reply to: