Re: [PRQ#59191] Deletion Request for widevine Rejected

2024-06-01 Thread Muflone
Hello again To be honest, my preference would still be to merge both packages under the "widevine" name.  I'm willing to maintain such a merged package. It won't happen as chromium-widevine is way more more popular, still maintained, has a huge number of votes and comments, while

Re: [PRQ#59191] Deletion Request for widevine Rejected

2024-06-01 Thread Bart De Vries
Hi Fabio, To be honest, my preference would still be to merge both packages under the "widevine" name.  I'm willing to maintain such a merged package. It won't happen as chromium-widevine is way more more popular, still maintained, has a huge number of votes and comments, while widevine is

Re: [PRQ#59191] Deletion Request for widevine Rejected

2024-06-01 Thread Muflone
Hi Bart To be honest, my preference would still be to merge both packages under the "widevine" name.  I'm willing to maintain such a merged package. It won't happen as chromium-widevine is way more more popular, still maintained, has a huge number of votes and comments, while widevine is

Re: [PRQ#59191] Deletion Request for widevine Rejected

2024-05-30 Thread Bart De Vries
On 12/05/2024 14:06, Muflone wrote: 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

Re: [PRQ#59191] Deletion Request for widevine Rejected

2024-05-12 Thread Muflone
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

Re: [PRQ#59191] Deletion Request for widevine Rejected

2024-05-06 Thread Bart De Vries
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

Re: [PRQ#59191] Deletion Request for widevine Rejected

2024-04-29 Thread Muflone
Hello Request #59191 has been Rejected by Muflone [1]: see previous package maintainer answer [1]https://aur.archlinux.org/account/Muflone/ @Muflone, what do you mean exactly? The package is not buildable and installable on Arch Linux due to missing a dependency, 'glibc-widevine'. That

Re: [PRQ#59191] Deletion Request for widevine Rejected

2024-04-28 Thread Marcell Meszaros
On 28 April 2024 18:48:44 GMT+02:00, Muflone wrote: > >>> Request #59191 has been Rejected by Muflone [1]: >>> >>> see previous package maintainer answer >>> >>> [1] https://aur.archlinux.org/account/Muflone/ >> @Muflone, what do you mean exactly? >> >> The package is not buildable and

Re: [PRQ#59191] Deletion Request for widevine Rejected

2024-04-28 Thread Muflone
Request #59191 has been Rejected by Muflone [1]: see previous package maintainer answer [1] https://aur.archlinux.org/account/Muflone/ @Muflone, what do you mean exactly? The package is not buildable and installable on Arch Linux due to missing a dependency, 'glibc-widevine'. That was an

Re: [PRQ#59191] Deletion Request for widevine Rejected

2024-04-28 Thread Marcell Meszaros
On 28 April 2024 17:29:00 GMT+02:00, not...@aur.archlinux.org wrote: >Request #59191 has been Rejected by Muflone [1]: > >see previous package maintainer answer > >[1] https://aur.archlinux.org/account/Muflone/ @Muflone, what do you mean exactly? The package is not buildable and installable on

[PRQ#59191] Deletion Request for widevine Rejected

2024-04-28 Thread notify
Request #59191 has been Rejected by Muflone [1]: see previous package maintainer answer [1] https://aur.archlinux.org/account/Muflone/