Re: Simple questions
Steve Langasek writes:
> Hmm. Well, you could write a package, un-task-kde, that conflicts with
> everything task-kde depends on...
That might prove inconvenient when the user tried to reinstall task-kde.
However, a method of removing tasks that actually removed the packages
pulled in by the tasks would be useful. How about a task-xxx-uninstaller
executable that would be pulled in by task-xxx and, when executed, would
remove task-xxx and everything it had pulled in? It would, of course, have
to dodge around packages depended on by things outside task-xxx, and it
would be helpful if 'dpkg -r task-xxx' could tell the user about
email@example.com (John Hasler)
Dancing Horse Hill