Shengjing Zhu <zhsj@debian.org> writes: > On Thu, Dec 12, 2024 at 6:59 AM Simon Josefsson <simon@josefsson.org> wrote: >> >> ons 2024-12-11 klockan 21:01 +0000 skrev Martin Dosch: >> > Dear Simon, >> > >> > Am 11.12.2024 20:59, schrieb Simon Josefsson: >> > > The naming of golang-go.gearno-encoding-base58 is a bit weird, how >> > > about >> > > golang-github-gearnode-base58 and golang-github-gearnode-base58-dev >> > > instead? What is the Go team policy on this? >> > >> > as this name was created by dh-make-golang I assumed it follows the >> > policy. But let's wait and see what some more experienced Go team >> > members think on that one. >> >> I suppose that's good enough for me, but let's see if anyone responds >> within 2 days or I'll do the upload. I think the documented naming >> guide is broken, I think we only rarely follow this advice: >> >> https://go-team.pages.debian.net/packaging.html#_naming_conventions >> >> In your case, that would suggest using 'base85' as the source package >> name, which I don't think is a good idea generally. > > You refer to the wrong section, please read > https://go-team.pages.debian.net/packaging.html#_naming_conventions_2 > Martin and dh-make-golang are right. I was talking about the source package name above. I'm confused now, which one do you suggest? 1) dh-make-golang-style: Source: golang-go.gearno-encoding-base58 Package: golang-go.gearno-encoding-base58-dev 2) Our policy documents, two links above: Source: base58 Package: golang-go.gearno-encoding-base58-dev 3) My initial suggestion Source: golang-github-gearno-base58 Package: golang-github-gearno-base58-dev 4) My revised suggestion Source: golang-github-gearno-base58 Package: golang-go.gearno-encoding-base58-dev 5) Something else? /Simon
Attachment:
signature.asc
Description: PGP signature