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.

Hi!

On Mon, 2026-04-27 at 23:00:09 +0200, Simon Josefsson wrote:
> Sean Whitton <[email protected]> writes:
> > Guillem Jover [24/Apr  2:01pm +02] wrote:
> >> 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'?

This still seems extremely generic to me, it just combines the generic
name with the VCS it supports, to me it would be similar to editor vs
editor-txt (or something along those lines).

> 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.

That's rather unfortunate. :/

> 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?

Yeah, I'm afraid this is not acceptable (see Debian Policy §10.1),
neither for the binary package name nor the program name. And as has
been mentioned makes the BTS very confusing when a binary package does
not come from the source package with the same name.

> 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?

This could be brought up on [email protected], otherwise I
guess the three other alternatives that come to mind, would be to either
try to find another upstream project that provides similar functionality,
fork with a better name, or not package it. :/

Thanks,
Guillem