Subject: Re: dependence on logical service vs. package name (was Re: RFC: new variable SUGGESTS, Part II)
To: None <email@example.com>
From: Martin J. Laubach <firstname.lastname@example.org>
Date: 09/06/2002 12:17:06
| You will need something to resolve that "service" then.
| Have fun coding a pkg manager!
Let me summarize my (probably not quite ripe yet) brainstormed ideas.
Suppose we have some packages
sendmail (provides "service-MTA")
exim (provides "service-MTA")
cron (depends on an "service-MTA" being present)
When one installs sendmail/exim, it registers an additional package
"service-MTA" (or whatever, I'm not attached to those names), which
depends on the package just installed (ie. sendmail/exim).
When you deinstall sendmail/exim, the service-MTA package will go
too because of the dependency.
Suppose I have installed sendmail and try to install exim, then
the package system should check whether a "service-MTA" is already
installed and warn me of a conflict (just like we have today, just
the conflicts don't have to be explicitely named -- simplifies things
quite a bit).
Things dependent on the service package could just use normal
This does not sound all that difficult. Is any crucial part