Hello
Il 06/05/24 11:20, Bart De Vries ha scritto:
Hi,
The chromium-widevine package only covers chromium and
chromium-derivatives (and only x86_64), as evidenced by it being
installed into `/usr/lib/chromium` where (only) chromium will find it
automatically.
As the pinned comment for chromium-widevine already mentions, this is
not strictly needed anymore, since most browsers these days are able
to download the widevine libs automatically from google on first use,
and install them into the user profile directory in `/home/user`.
The unique thing about this package is that it can install the
widevine binaries in a central location in `/opt`, and will register
the libs with chromium and firefox to use them from that central
location with no user setup required. This avoids having multiple
copies for each browser and user.
Therefore, apart the browsers registration, this package offers the same
content of chromium-widevine, I suppose.
Its plus is registering the same plugin in multiple browsers location.
So in the end, why don't you simply use the chromium-widevine dependency
to download the library and create the needed configuration for the
others browsers?
This wouldn't result in a duplicate package, a more simpler maintenance
and also better a more specific task for the package.
All the rest seems not an interesting argument against the package deletion.
Regards
--
Fabio Castelli aka Muflone
