Bug#282283: Adopting dselect, or not

[Nathanael Nerode <neroden@fastmail.fm>]

I love dselect and would like to take it over; I prefer it to aptitude -- but 
I'm not ready to take it over yet.

The problem is that it currently has an incestuous relationship with the dpkg 
source.  I am afraid to touch anything or do any cleanup for fear of breaking 
dpkg.

If someone can manage to break this Siamese-twin relationship, so that dselect 
can build *after* dpkg (based on a fixed collection of headers exported by 
dpkg, and possibly some duplicated C files), rather than at the same time, then 
I would be happy to take it over.  I'm also happy to help in severing the 
Siamese twins, but I haven't been able to figure out how to do so yet.

I think separating the Siamese twins is worthwhile for dpkg as well.

I guess I said something like this before.  But if anyone can help in breaking 
the linkage, it would be really helpful.  Consider this an "RFH for an RFH".

-- 
Nathanael Nerode  <neroden@fastmail.fm>

[Insert famous quote here]