Bug#450915: file conflicts between packages

[Niko Tyni]

On Mon, Nov 12, 2007 at 08:13:43AM +0100, Michael Ablassmeier wrote:
> Package: par, libpar-packer-perl
> Severity: serious
> Justification: policy violation
 
> both par and libpar-packer-perl do ship `/usr/bin/par' but neither conflict or
> add a diversion, thus fail to be installed in the same environment:

Hi,

the libpar-packer-perl version used to be in libpar-perl and was called
par.pl. I think the name got accidentally changed when part of libpar-perl
was split into libpar-packer-perl.

The par package clearly has a better claim to the name. I'll change the
libpar-packer-perl version back into par.pl at least until we come up
with a better solution wrt. policy 10.4:

  When scripts are installed into a directory in the system PATH, the
  script name should not include an extension such as `.sh' or `.pl'
  that denotes the scripting language currently used to implement it.

Cheers,
--
Niko Tyni   ntyni at iki.fi