Re: "dselect" replacement team
Tom Lees <email@example.com> writes:
> I would think it would be a bit more general than "a clone of dselect with
> different keys and colours" - a complete re-implementation of the
> packaging system so that the user interface is distinctly separate from
> the underly mechanisms, which are distinctly separate from the low-level
> access code would be very nice.
If this is done well, one would be able to simply run the result
through SWIG to generate interfaces for Perl/Python/Tcl, etc.
So please, implementors, be devoted to the notion of separating the
interface and the backend---and document it well.