[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 06/15: gnu: wesnoth-server: Rename package to the-battle-for-wesnoth
From: |
Ludovic Courtès |
Subject: |
Re: 06/15: gnu: wesnoth-server: Rename package to the-battle-for-wesnoth-server. |
Date: |
Wed, 27 Mar 2019 12:11:16 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) |
Hello,
Andreas Enge <address@hidden> skribis:
> On Tue, Mar 26, 2019 at 04:32:46PM +0100, Pierre Neidhardt wrote:
>> Sorry, I misunderstood the conclusion of the discussion: I thought that
>> we would simply follow the package naming convention as per the manual.
>
> I am confused about this statement. The naming convention speaks a bit
> vaguely of "project name chosen upstream"; very often, this means the
> tarball name. Now there is www.wesnoth.org, which distributes tarballs and
> executable files called wesnoth.*. So I would argue that the upstream
> name is "wesnoth" and would suggest to revert this change.
+1
I agree with Ricardo that prior discussion would have been necessary. I
think it’s now clear that this case does not fall under the
“non-controversial” category that ‘HACKING’ mentions.
Thanks,
Ludo’.