Re: About the intentionally duplicated package wechat-beta-bwrap and wechat-universal and unmaintained orginal package wechat-uos

2025-01-02 Thread S Umple
> Hello, I'm 7Ji, maintainer of wechat-universal-bwrap[a] (wrongly typed as wechat-universal in Kimiblock's original mail), and co-maintainer of wechat-beta-bwrap[b]. leaeasy[c], the maintainer of -beta, is my friend. I think it's necessary for me to clear up some misunderstanding and introduce the

Re: AUR guideline on `Duplicate` packages, and Package Maintainers

2025-01-02 Thread S Umple
(sorry about the formatting. resend) It's good that this is an open discussion so we can get all the facts and misinformation presented for everyone to see and judge. Let's get the main points addressed first. Details are next. This is the subject of this discussion and the main points are abo

Re: AUR guideline on `Duplicate` packages, and Package Maintainers

2025-01-02 Thread S Umple
It's good that this is an open discussion so we can get all the facts and misinformation presented for everyone to see and judge. Let's get the main points addressed first. Details are next. This is the subject of this discussion and the main points are about: ** AUR guideline on `Duplicate` pa

Re: AUR guideline on `Duplicate` packages, and Package Maintainers

2025-01-02 Thread S Umple
Update [4] On Thu, Jan 2, 2025 at 9:57 AM S Umple wrote: > Recently there's been a debacle about the wechat packaging in AUR. > Essentially there were two competing packages wechat and wechat-bin [1] > which are both popular. Package maintainer K(type user in AUR) of wechat >

AUR guideline on `Duplicate` packages, and Package Maintainers

2025-01-02 Thread S Umple
Recently there's been a debacle about the wechat packaging in AUR. Essentially there were two competing packages wechat and wechat-bin [1] which are both popular. Package maintainer K(type user in AUR) of wechat took unbelievable measures to try to get rid of wechat-bin from AUR to begin with and w