Sebastian Kuzminsky wrote: > All packages which supply an instance of a common command name (or, in > general, filename) should generally use update-alternatives, so that > they may be installed together. If update-alternatives is not used, > then each package must use Conflicts to ensure that other packages > are de-installed.
Two different packages must not install programs with different
functionality but with the same filenames.
[...]
If this case happens, one of the programs must be renamed.
-- policy 10.1.
> So, I'm proposing this:
>
> GNU Interactive Tools installs /usr/bin/git.shell (or something)
>
> Cogito installs /usr/bin/git.scm (or something)
>
> update-alternatives is used to make one of those appear as
> /usr/bin/git
Yeah and people who want to deal with kernel sources would complicate
this scenario greatly. And then someone might package "rm" as "git" just
to prove the point. There's a reason we don't do this.
--
see shy jo
signature.asc
Description: Digital signature
