Automatic alias request for devpack-for-go: dlv, gotests

name: devpack-for-go

description: Current, tested Go development tools (Delve, gopls, golangci-lint, govulncheck, gotests, gofumpt) in one maintained snap. The tools run against the Go installation selected by the user’s PATH.

store: https://snapcraft.io/devpack-for-go

snap-id: J2LLUHu4cHhSayCVOmJ9BuVcuL2i86Xu

publisher: Canonical**

source: GitHub - canonical/devpack-for-go: Go development tools companion snap for the official Go snap · GitHub

spec: FO137 - devpack-for-go snap to provide tools for Go developers

aliases: dlv: devpack-for-go.dlv gotests: devpack-for-go.gotests

reasoning: dlv and gotests are the upstream command names for Delve ( GitHub - go-delve/delve: Delve is a debugger for the Go programming language. · GitHub ) and gotests ( GitHub - cweill/gotests: Automatically generate Go test boilerplate from your source code. · GitHub ). Upstream documentation, editor integration, and the VS Code Go extension all invoke them under those names. devpack-for-go is the Canonical-published Go devpack and builds these tools from their pinned upstream releases, so the aliases resolve to exactly the commands users expect. The previous revision told users to create these aliases by hand with sudo snap alias; automatic aliases remove that manual step.

conflicts: the store has no snap named dlv, delve, or gotests, and I could not find another snap shipping a dlv or gotests command.

deliberately not requested: this snap also bundles gopls, golangci-lint, govulncheck, and gofumpt. We are not requesting those aliases because the store already has snaps holding those names — gopls (alexmurray*), golangci-lint (golangci**, the upstream project’s own snap), govulncheck (sespiros), and gofumpt (holmanb). devpack-for-go users keep the snap-qualified names (devpack-for-go.gopls, devpack-for-go.golangci-lint, …) for those tools, which is what our editor configuration writes into VS Code, Vim, Neovim, and Emacs.

release status: the aliases are declared in the 2026.10.1 revision we want to launch with this PR.

This request has been added to the queue for review by the @reviewers team.

Hello @levihackerman-102,

We tend to be restrictive for 3 letter aliases, but I believe in this case dlv is well-known enough to qualify as a reasonable request. This is a +1 from me for granting the well-known aliases dlv and gotest to snap devpack-for-go. What do other reviewers think?

Hi folks!

I agree with @elisehdy, in this case both aliases look appropriate to me (+1).

Regarding the other tools bundled in the snap, I think it may possibly be appropriate to also grant aliases for them. I’m unsure what the default behavior would be if both snaps are installed (I don’t know what alias would take priority by default), but the user should always be able to establish their preferred one with sudo snap prefer <snap-name>.

@alexmurray I’m quite interested about your thoughts about this as a snap maintainer and as a reviewer.

Thanks!

Hey folks

This is an interesting question - and I think it really comes down to trying to meet the end users expectations and being consistent. devpack-for-go clearly states that it bundles all these tools so if a user installs it then I think it is safe to assume they would expect all of them to be directly available without having to use the devpack-for-go prefix. I would prefer that either all or none of the aliases are granted - but on balance I think that all should likely be granted for consistency (including gopls, golangci-lint, govulncheck and gofumpt).

If we also consider a user who has installed a standalone gopls / golangci-lint snap who then installs devpack-for-go, PERHAPS it would be surprising for them to find that the devpack-for-go versions of these tools are then aliased instead of their original gopls etc - but that is just the nature of having so many variants of the same things in the store. Also, I would expect that if you install devpack-for-go then you would use all of its versions of the tools rather than say some as their standalone snaps and others as the devpack-for-go bundled ones.

So my preference would be to grant ALL aliases including gopls / golangci-lint etc as well.

As @jslarraz said, users can always use snap prefer in the end OR just invoke their preferred tool as $SNAP_NAME.$APP anyway.

So +1 from me to grant the requested aliases PLUS the non-requested ones (gopls / govulncheck / golangci-lint etc)

1 Like

Thank you for the input @jslarraz and @alexmurray!

@levihackerman-102 given the above discussion, do you have any concerns with us granting aliases for all the tools bundled with devpack-for-go instead of just the requested ones?