Re: Bug#1134655: ITP: forge -- Go library and CLI for working with git forges. Supports GitHub, GitLab, Gitea/Forgejo, and Bitbucket Cloud through a single interface.

Simon Josefsson <[email protected]>
Newsgroups gmane.linux.debian.devel.general
Message-ID <[email protected]>
Sean Whitton <[email protected]> writes:

> Guillem Jover [24/Apr  2:01pm +02] wrote:
>> Hi!
>>
>> On Wed, 2026-04-22 at 22:12:55 +0200, Simon Josefsson wrote:
>>> Package: wnpp
>>> Severity: wishlist
>>> Owner: Simon Josefsson <[email protected]>
>>>
>>> * Package name    : forge
>>>   Version         : 0.4.0-1
>>>   Upstream Author : Andrew Nesbitt
>>> * URL             : https://github.com/git-pkgs/forge
>>> * License         : Expat
>>>   Programming Lang: Go
>>>   Description     : Go library and CLI for working with git forges. Supports GitHub, GitLab, Gitea/Forgejo, and Bitbucket Cloud through a single interface.
>>>
>>>  Go library and CLI for working with git forges. Supports GitHub, GitLab,
>>>  Gitea/Forgejo, and Bitbucket Cloud through a single interface.
>>>
>>> https://salsa.debian.org/go-team/packages/forge
>>> https://salsa.debian.org/jas/forge/-/pipelines
>>
>> This uses an extremely generic name for the package and program,
>> please rename this (or ideally ask upstream in the existing ticket
>> you filed) to something more unique.
>
> I agree, 'forge' is extremely generic.

Agreed.  And it is already used in Debian, so impossible to re-use:

https://tracker.debian.org/pkg/forge

What do people think would be a better name for the source package?  Any
objections to 'forge-git'?  Sometimes names like 'forge-go' or
'forge-golang' is used, but I've always found them a bit ugly.  I find
'forge-git' a bit more descriptive of what it does.

Upstream replied and will not rename the project.  I think shipping
/usr/bin/forge with a Conflicts:snap (which also provides
/usr/bin/forge) in a binary package 'forge' would be acceptable.  Any
objections?  Renaming the binary names of upstream in Debian will be
quite confusing, unless there is any consensus between
RedHat/ArchLinux/Guix/etc to use the same non-upstream name.  And I
doubt we'll achieve that.  Is there some other reasonable alternative?

/Simon
signature.asc (application/pgp-signature, 1.2 KB)
-----BEGIN PGP SIGNATURE-----

iQNoBAEWCgMQFiEEo8ychwudMQq61M8vUXIrCP5HRaIFAmnvzlkUHHNpbW9uQGpv
c2Vmc3Nvbi5vcmfCHCYAmDMEXJLOtBYJKwYBBAHaRw8BAQdACIcrZIvhrxDBkK9f
V+QlTmXxo2naObDuGtw58YaxlOu0JVNpbW9uIEpvc2Vmc3NvbiA8c2ltb25Aam9z
ZWZzc29uLm9yZz6IlgQTFggAPgIbAwULCQgHAgYVCAkKCwIEFgIDAQIeAQIXgBYh
BLHSvRN1vst4TPT4xNc89jjFPAa+BQJp4fWRBQkOa+rdAAoJENc89jjFPAa+hWIA
/1lQvrJeGlQq50lP6tm99D1zDy7J1tQ3ha4x0Jx7rkFTAP9hpUKuTvm6m1fXyiZV
YZlu2+Id/Dq3CIAZvNF+XEr2BLgzBFySz4EWCSsGAQQB2kcPAQEHQOxTCIOaeXAx
I2hIX4HK9bQTpNVei708oNr1Klm8qCGKiPUEGBYIACYCGwIWIQSx0r0Tdb7LeEz0
+MTXPPY4xTwGvgUCaeCW1wUJDmqLVgCBdiAEGRYIAB0WIQSjzJyHC50xCrrUzy9R
cisI/kdFogUCXJLPgQAKCRBRcisI/kdFoqdMAQCgH45aseZgIrwKOvUOA9QfsmeE
8GZHYNuFHmM9FEQS6AD6A4x5aYvoY6lo98pgtw2HPDhmcCXFItjXCrV4A0GmJA4J
ENc89jjFPAa+s7AA+gIIHpBApDpcDj1sKhzDngmpvwQf0VkHme6s+EG7qSgpAQDe
/XMrU0c0Pa3ji85cMqZhvzJOFI/soe662lzL0QY3Bbg4BFySz2oSCisGAQQBl1UB
BQEBB0AxlRumDW6nZY7A+VCfek9VpEx6PJmdJyYPt3lNHMd6HAMBCAeIfgQYFggA
JgIbDBYhBLHSvRN1vst4TPT4xNc89jjFPAa+BQJp4JbXBQkOaottAAoJENc89jjF
PAa+RNUA/2faQO/nFT06E+MlhlQdo/0chlQXC5TZMPTVvVBFwoLOAP9xLJK0ow5E
jTzYJB4K810AL/Iv6PEOAEgA4cPTHVlbCQAKCRBRcisI/kdFohmnAP9m5bac17H6
W0gep6OP1A/IYr2lcP0oi4dnnqQg06XppwD/Qr9PVnyIF9hJl8QBnebHk2n5/Lrt
6/FT35i/ZOz23QU=
=6AcB
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.