[PRQ#59755] Deletion Request for pipewire-common-git
eh5 [1] filed a deletion request for pipewire-common-git [2]: No intention to keep maintaining. [1] https://aur.archlinux.org/account/eh5/ [2] https://aur.archlinux.org/pkgbase/pipewire-common-git/
On 29 April 2024 04:21:36 GMT+02:00, notify@aur.archlinux.org wrote:
eh5 [1] filed a deletion request for pipewire-common-git [2]:
No intention to keep maintaining.
[1] https://aur.archlinux.org/account/eh5/ [2] https://aur.archlinux.org/pkgbase/pipewire-common-git/
+1 for deletion, as this is a duplicate of AUR/pipewire-git [a] with wrong, misleading name. @eh5 chose the name qualifier "common", which is something that is typically used by some split packages when there are some files needed by all main split packages (e.g. in the Arch/extra pkgbase 'gnome-desktop', there are subpackages 'gnome-desktop', 'gnome-desktop-4', 'gnome-desktop-common'). But pipewire-common-git is not part of the pipewire-git pkgbase, it builds the main pipewire code, just like AUR/pipewire-git. @eh5 also chose not to collaborate with the active maintainer of AUR/pipewire-git and instead chose to create a duplicate, which is not something that is favored on AUR. Earlier I submitted a deletion request for this duplicate "common" package, but the responding PM chose to reject that and to keep this package, citing maintainer's statement that this is better. So I was contemplating filing a deletion request for the broken but correctly named pipewire-git. With this deletion request filed by the owner of pipewire-common-git, if accepted, AUR/pipewire-git will become yet again the canonical VCS package for pipewire. Anyone wishing to test or use a VCS build of pipewire can check out pipewire-git. It is currently in a neglected state and has been broken for quite some time. It is also in misalignment with how extra/pipewire is packaged. But its maintainer is very active when prompted, and is open to feedback and collaboration. [a]: https://aur.archlinux.org/packages/pipewire-git
On 29 April 2024 12:07:49 GMT+02:00, Marcell Meszaros <marcell.meszaros@runbox.eu> wrote:
On 29 April 2024 04:21:36 GMT+02:00, notify@aur.archlinux.org wrote:
eh5 [1] filed a deletion request for pipewire-common-git [2]:
No intention to keep maintaining.
[1] https://aur.archlinux.org/account/eh5/ [2] https://aur.archlinux.org/pkgbase/pipewire-common-git/
+1 for deletion, as this is a duplicate of AUR/pipewire-git [a] with wrong, misleading name.
@eh5 chose the name qualifier "common", which is something that is typically used by some split packages when there are some files needed by all main split packages (e.g. in the Arch/extra pkgbase 'gnome-desktop', there are subpackages 'gnome-desktop', 'gnome-desktop-4', 'gnome-desktop-common').
But pipewire-common-git is not part of the pipewire-git pkgbase, it builds the main pipewire code, just like AUR/pipewire-git.
@eh5 also chose not to collaborate with the active maintainer of AUR/pipewire-git and instead chose to create a duplicate, which is not something that is favored on AUR.
Earlier I submitted a deletion request for this duplicate "common" package, but the responding PM chose to reject that and to keep this package, citing maintainer's statement that this is better. So I was contemplating filing a deletion request for the broken but correctly named pipewire-git. With this deletion request filed by the owner of pipewire-common-git, if accepted, AUR/pipewire-git will become yet again the canonical VCS package for pipewire.
Anyone wishing to test or use a VCS build of pipewire can check out pipewire-git. It is currently in a neglected state and has been broken for quite some time. It is also in misalignment with how extra/pipewire is packaged. But its maintainer is very active when prompted, and is open to feedback and collaboration.
As it turns out, AUR/pipewire-git is in much better shape than it was for years, as its maintainer has made a big modernization of that PKGBUILD two weeks ago, making it align well with repo's pipewire.
On 29 April 2024 12:07:49 GMT+02:00, Marcell Meszaros <marcell.meszaros@runbox.eu> wrote:
On 29 April 2024 04:21:36 GMT+02:00, notify@aur.archlinux.org wrote:
eh5 [1] filed a deletion request for pipewire-common-git [2]:
No intention to keep maintaining.
[1] https://aur.archlinux.org/account/eh5/ [2] https://aur.archlinux.org/pkgbase/pipewire-common-git/
+1 for deletion, as this is a duplicate of AUR/pipewire-git [a] with wrong, misleading name.
@eh5 chose the name qualifier "common", which is something that is typically used by some split packages when there are some files needed by all main split packages (e.g. in the Arch/extra pkgbase 'gnome-desktop', there are subpackages 'gnome-desktop', 'gnome-desktop-4', 'gnome-desktop-common').
But pipewire-common-git is not part of the pipewire-git pkgbase, it builds the main pipewire code, just like AUR/pipewire-git.
@eh5 also chose not to collaborate with the active maintainer of AUR/pipewire-git and instead chose to create a duplicate, which is not something that is favored on AUR.
Earlier I submitted a deletion request for this duplicate "common" package, but the responding PM chose to reject that and to keep this package, citing maintainer's statement that this is better. So I was contemplating filing a deletion request for the broken but correctly named pipewire-git. With this deletion request filed by the owner of pipewire-common-git, if accepted, AUR/pipewire-git will become yet again the canonical VCS package for pipewire.
Anyone wishing to test or use a VCS build of pipewire can check out pipewire-git. It is currently in a neglected state and has been broken for quite some time. It is also in misalignment with how extra/pipewire is packaged. But its maintainer is very active when prompted, and is open to feedback and collaboration.
As it turns out, AUR/pipewire-git is in much better shape than it was for years, as its maintainer has made a big modernization of that PKGBUILD two weeks ago, making it mostly align with repo's pipewire.
(Resend to mailing list.) On 4/29/24 18:07, Marcell Meszaros wrote:
On 29 April 2024 04:21:36 GMT+02:00, notify@aur.archlinux.org wrote:
eh5 [1] filed a deletion request for pipewire-common-git [2]:
No intention to keep maintaining.
[1] https://aur.archlinux.org/account/eh5/ [2] https://aur.archlinux.org/pkgbase/pipewire-common-git/
+1 for deletion, as this is a duplicate of AUR/pipewire-git [a] with wrong, misleading name.
Haven't you noticed I am the maintainer of pipewire-common-git? I filed the deletion request because the current PipeWire in master branch is not in a state for daily use, not because what you called "misleading name".
@eh5 chose the name qualifier "common", which is something that is typically used by some split packages when there are some files needed by all main split packages (e.g. in the Arch/extra pkgbase 'gnome-desktop', there are subpackages 'gnome-desktop', 'gnome-desktop-4', 'gnome-desktop-common').
But pipewire-common-git is not part of the pipewire-git pkgbase, it builds the main pipewire code, just like AUR/pipewire-git.
You can play the wording game as you own.
@eh5 also chose not to collaborate with the active maintainer of AUR/pipewire-git and instead chose to create a duplicate, which is not something that is favored on AUR.
It's the maintainer of pipewire-git chose not to collaborate with community, he persist not to add `gst-plugin-pipewire-git` into AUR/pipewire-git for unknown reason despise users have requested multiple times. That why I created pipewire-common-git. I have repeated this fact multiple times and you are just ignoring them, and you keep saying "duplicate". https://aur.archlinux.org/pkgbase/pipewire-common-git?O=50#comment-785408 Note the "gst-plugin-pipewire" is essential for screen-cast to work on some Wayland desktop implementation. Not to say it allows user to piping camera/video node in PipeWire graph in CLI without writing PipeWire client. And as the time I created pipewire-common-git, I was actively contributing and testing PipeWire, so a package with "common" feature set is more valuable for me personally.
Earlier I submitted a deletion request for this duplicate "common" package, but the responding PM chose to reject that and to keep this package, citing maintainer's statement that this is better. So I was contemplating filing a deletion request for the broken but correctly named pipewire-git. With this deletion request filed by the owner of pipewire-common-git, if accepted, AUR/pipewire-git will become yet again the canonical VCS package for pipewire.
It's because the reason you are giving for that deletion request, duplication, is just wrong. AUR allows packages for same software to coexists so long as they have different feature set and are not pure duplication.
Anyone wishing to test or use a VCS build of pipewire can check out pipewire-git. It is currently in a neglected state and has been broken for quite some time. It is also in misalignment with how extra/pipewire is packaged. But its maintainer is very active when prompted, and is open to feedback and collaboration.
There is still https://aur.archlinux.org/pkgbase/pipewire-full-git, it's a bigger set of "pipewire-common-git" so I chose not to file a deletion request for that. I quit the maintenance because I no longer put eyes on PipeWire's development activity, anyone interested can adopt that package. And end users should just use the stable PipeWire release instead.
Request #59755 has been Accepted by Muflone [1]: [Autogenerated] Accepted deletion for pipewire-common-git. [1] https://aur.archlinux.org/account/Muflone/
participants (4)
-
Huang-Huang Bao
-
Marcell Meszaros
-
Marcell Mészáros
-
notify＠aur.archlinux.org