On 4/19/21 4:55 AM, Henry-Joseph Audéoud wrote:

Hi all,

On 16/04/2021 02:04, notify@aur.archlinux.org wrote:

...

NoobAlice [1] filed a request to merge pidgin-window-merge [2] into pidgin-window_merge [3]:

Almost the same name, except this plugin misses the underscore_ in the official name from Github.  Same Github source.

[1] https://aur.archlinux.org/account/NoobAlice/ [2] https://aur.archlinux.org/pkgbase/pidgin-window-merge/ [3] https://aur.archlinux.org/pkgbase/pidgin-window_merge/

I maintain pidgin-window-merge [1].  I do not know how I did not found pidgin-window_merge [2] previously.  I agree that both packages build the same upstream.  The difference is that pidgin-window_merge [2] builds upstream version 0.3 and pidgin-window-merge [1] builds the last commit.

So IMHO pidgin-window_merge [2] should be kept (its the last official upstream release), and pidgin-window-merge [1] should in any way be replaced by pidgin-window[-_]merge-git.  I agree to push my package as -git.  May I have some opinions on that beforehand?

Is there a clear rule indicating if one should use - or _ in the AUR package name this particular context?

P.S.: some history: - 2012-04, pidgin-window_merge [2] on AUR - 2012-07, window_merge upstream version 0.3 - 2013-05, last window_merge upstream commit - 2015-07, last pidgin-window_merge [2] update - 2019-03, pidgin-window-merge [1] on AUR - 2020-10, last pidgin-window-merge [1] update

Normally, if this were an active project, there could be packages of pidgin-window_merge and pidgin-window_merge-git if people wanted both. Since this software has not seen commits in 8 years, do we really need two versions? Are there big changes in the post-0.3 commits that make the package work better? My opinion is that one PKGBUILD for this unchanging software is enough. The - vs _ in the AUR name for this package is based on the upstream name that the software creator used. The software creator dm0- on Github named it window_merge, so we should use that name. Normally I think - is used instead of spaces in package names. FYI - For making a -git package, it is normal to write your PKGBUILD so that users will automatically get the git repository as it is when they use it, not what the repo looked like on the day you wrote the PKGBUILD. See this link: https://wiki.archlinux.org/index.php/VCS_package_guidelines#The_pkgver()_fun... P.S. I am VERY inexperienced with the AUR submissions rules, so if any more experienced users or TUs want to correct anything I've said, please do! P.P.S. Apologies in advance if my mailing list etiquette is off. I haven't sent to it directly before. I am including AUR maintainer audeoudh 's full message above, as for some reason it does not appear to be showing up in the online aur-requests archive. ??? https://lists.archlinux.org/pipermail/aur-requests/2021-April/thread.html