Summary: | ports-mgmt/pkg does not respect CONFLICTS_INSTALL | ||
---|---|---|---|
Product: | Ports & Packages | Reporter: | Matthias Fechner <mfechner> |
Component: | Individual Port(s) | Assignee: | freebsd-pkg (Nobody) <pkg> |
Status: | Closed Works As Intended | ||
Severity: | Affects Some People | CC: | freebsd, lwhsu |
Priority: | --- | ||
Version: | Latest | ||
Hardware: | Any | ||
OS: | Any | ||
Bug Depends on: | |||
Bug Blocks: | 225309 |
Description
Matthias Fechner
2019-01-09 22:01:21 UTC
pkg does automatically figure out those conflict making CONFLICT_INSTALL useless. There is no need to do anything but let pkg figure it out I think what mfechner@ means is the conflict happens at the run time, not during the install time so pkg will not know about it. Having a way to manually mark the ports conflict (carefully) might be a good idea. For those two ports, they only conflict if you try to use them at the same time, which nobody will. do you have an example of such ports? with real conflicts at runtime? yes, it is in the problem description: One example is www/gitlab-ce and devel/gitolite in this case I don't think pkg should handle the conflict, this is up to the administrator to do it. the administrator can configure both to use a .ssh/authorized_keys elsewhere. dealing with the conflicts, will probably solve an issue for 2 administrators, but will for sure be painful for most others. |