Re: Policy on pkgs with same filename and QA rant (was: Re: Mercury compiler (policy, anybody)?)
Chris Fearnley <email@example.com> writes:
> >``It is not allowed that two packages install programs with different
> >functionality but with the same filenames. (The case of two programs
> >having the same functionality but different implementations is handled via
> >`alternatives.') If this case happens, one of the programs has to be
> >renamed. The maintainers should report this to the developers' mailing
> >list where it will be dicussed. The VP of Engineering will make a final
> >decision which program has to be renamed.''
> Kill the last sentence replacing it with: "If consensus can not be
> reached, the two packages will have to conflict with each other."
Or better: if consensus can not be reached, BOTH programs must be
That's basically a stick to force developers to reach a consensus.
Incidentally, the Contents file currently lists only the first
instance of a program, but I can make it list all file instances.
(not all directory instances obviously, as otherwise we'd have 100s of
entriess for /usr/).
A long term goal is for dpkg to have the --force-overwrite flag off by
default. Brian - you should probably add that to your list as things
to do for future versions.