Summary: | Two init scripts with same 'provide' for a virtual dependency conflict | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Kevin Spicer <kevin> |
Component: | [OLD] baselayout | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | gavin, zaai |
Priority: | High | Keywords: | InVCS |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 36060, 140865 | ||
Attachments: |
patch to /etc/conf.d/rc
patch to /sbin/depscan.sh patch to /lib/rcscripts/awk/gendepends.awk |
Description
Kevin Spicer
2004-04-05 14:45:34 UTC
Created attachment 28758 [details, diff]
patch to /etc/conf.d/rc
Created attachment 28759 [details, diff]
patch to /sbin/depscan.sh
Created attachment 28760 [details, diff]
patch to /lib/rcscripts/awk/gendepends.awk
Would it be a solution to have selection of the correct package done automagically by looking at the users setting in rc-update? The package that is selected to start is the one to go with, the package that is disabled by default is ignored. It will not work for every package or setup but at least will catch most of them (like MailScanner). You must disable sendmail in rc-update and enable the sendmail script which invokes sendmail. Just my $0.02 :) *** Bug 62778 has been marked as a duplicate of this bug. *** In Redhat there is something called alternative. Where it let you select one of the few program which providing the same services. Shouldn't that be some hints? Latest SVN Changelog in trunk It is now possible to have >1 service that can provide foo. If something then uses foo it selects which service to depend on using the following criteria - not stopped, in runlevel, alphabetical. :) The only downside of my approach is that depscan.sh will not spit out any circular deps caused by the provides. Well be in baselayout-1.13 baselayout-1.13.0_alpha1 is in portage, although p.masked So this is finally fixed :) *** Bug 156738 has been marked as a duplicate of this bug. *** |