Package: libdvd-pkg
Version: 1.4.2-1-1
Severity: normal
Dear Maintainer,
My use case is the simple one, all I want is to play some DVDs with my
media player of choice. All I need is the libdvdcss2 binary package.
I don't need libdvd-pkg and all the build tools that come with it for
that, so perhaps I want to remove them after building the package, or
perhaps they were never installed to begin with because I built the
libdvdcss2 package in a chroot or on another host.
However the libdvdcss packages built by libdvd-pkg declare a dependency
on libdvd-pkg. That's incorrect, inconvenient for some people, and a
violation of the Debian policy on dependencies.
I see that the code responsible for this is in b-i_libdvdcss.sh:
> ## inject ${PKGI} to guest package Depends to uninstall generated packages on
> installer remove.
> perl -pi -e "s{^Depends:\K}{ ${PKGI}, }mg" debian/control
I had to comment this out.
I understand the stated rationale, however it has drawbacks as mentioned
above, and it still is incorrect and an abuse of the dependency
mechanism.
The script itself installs the built packages with `dpkg -i`, does that
cause issues preventing from relying on the cleanup mechanisms of the
usual package managers?
Note that there are other strategies than having libdvd-pkg installed on
the user's host to install and update libdvdcss: for example it could
be built by the organization's administrator and distributed through an
internal package repository.
Regards,
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8),
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
