On Tue, 1 May 2001, Steve Greenland wrote:
> On 01-May-01, 12:50 (CDT), Vince Mulhollon <[EMAIL PROTECTED]> wrote:
> > On 05/01/2001 12:40:24 PM roland wrote:
> > >> Vince Mulhollon wrote:
> > >> > From my poor memory, the "generally agreed best idea" is to setup two
> > >> > packages, vaguely like this:
> > >> >
> > >> > Package name: task-abc
> > >> > Conflicts: task-abc-remove
> > >> > Depends: abc, bcd, cde, def
> > >> >
> > >> > Package name: task-abc-remove
> > >> > Conflicts: task-abc, abc, bcd, cde, def
> > >>
> > >> Please, NO! This is a pretty ugly hack and there are better ways to do
> > >> this, e.g. the debfoster aproach. I don't agree at all with you that
> > >> this is the "generally agreed best idea". Rather the opposite.
> >
> > Oh, I don't know if it's an ugly hack.
>
> Well, one reason it's ugly is that your -remove "tasks" will show up in
> the Task Selection dialog that runs before the initial install. I expect
> that many new users would be rather confused...
It's also an ugly hack because you'll have to:
apt-get install { <task-name>-remove }
which happens to be REALLY ugly. Better to have apt-get support
task-removals. For example:
apt-get remove --remove-task [--purge] { <task-name> }
Simon
