On 2025-02-26 15:55:06 +0100, Helmut Grohne wrote:
> Of course this does not consider conflicts, so in practice we have
> some false positives. Here is an example output.
[...]
As the policy is written, a Conflicts does not seem to be a resolution
for programs with the same filenames:
10.1
Two different packages must not install programs with different
functionality to the same filenames, even names under different
directories, when the directories are on the default PATH.
There is no mention of non-conflicting packages here (such as
"Two different non-conflicting packages"), and it does not say that
this concerns simultaneous installations (or on the same machine).
As I understand it, if a program name "foo" comes from conflicting
packages A and B, this may confuse the user and possibly scripts
(or configuration in applications that run other programs) if
package A is installed on some machine and package B is installed
on another machine, or if some day on some machine, package A gets
removed and package B gets installed. This could be a reason why
such a case may be forbidden, just like for non-conflicting
packages.
Moreover, if the program "foo" does not do the same thing in these
two packages A and B, then the user may want to be able to use both
programs on the same installation, which would be possible if the
program names were different (avoiding the package conflict).
--
Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / Pascaline project (LIP, ENS-Lyon)
