Re: Simple questions
On Fri, Apr 06, 2001 at 01:29:31PM +0900, Olaf Meeuwissen wrote:
> John Hasler <firstname.lastname@example.org> writes:
> > 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
No! Every task-package pulls in a set of libraries that might
also be needed by other packages. There is no clean way of
getting rid of these libraries, too, as they probably are
dependencies for other tasks.
> Hmm, not exactly what you suggest, but have a look at debfoster.
# apt-get install debfoster
# debfoster -q (only needed after installation)
# debfoster task-kde-
And no need to mess around with the keepers file (which did move,
16 Hard coded constant for amount of room allowed for
cache align and faster forwarding (tunable)
-- seen in /usr/src/linux-2.2.14/net/TUNABLE