of virtual packages and services
Just a thought on the fingerd thread. What about having a general policy
for network services in that perform a function. Basically it would say
something like:
A package which provides a network service can opt to Provide this
service via a virtual package. The name of the virtual package
provided is in the format "<serv>-service" where <serv> is the
corresponding name in /etc/services that matches the standard port
of the service that it provides. A package cannot provide a
service unless it meets the requirements of that service. It also
cannot provide a servce which does not exist in the Debian default
/etc/services file. Examples:
Package: openldapd
Provides: ldap-service
Package: exim
Provides: smtp-service
Note, unless a package contains a mechanism that allows it to be
installed at the same time as other packages which provide the
same service (either by disabling itself, or configuring itself to
run on an alternate port) it should also Conflict with the same
virtual package that it provides. This is also true if the
packages contain files of the same name, and are not using
alternatives.
This would seem to cover all current and future instances of this
reoccuring situation.
Ben
--
-----------=======-=-======-=========-----------=====------------=-=------
/ Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \
` bcollins@debian.org -- bcollins@openldap.org -- bcollins@linux.com '
`---=========------=======-------------=-=-----=-===-======-------=--=---'
Reply to: