Hi Mathias, On Mon Jul 28, 2025 at 3:39 PM CEST, Mathias Gibbens wrote:
Hmm, yes this is less than ideal. There appear to be no actual reverse dependencies on golang-github-mitchellh-hashstructure-v2-dev, while golang-github-mitchellh-hashstructure-dev has 47.
Oh, that's higher than I though. Are you counting direct dependencies, or transitive ones too?
I'd suggest modifying this bug into a RM request for golang-github-mitchellh-hashstructure-v2-dev; CC'ing Arthur who had originally uploaded the v2 package for an ACK from him first.
When hashstructure-v2 was uploaded, hashstructure was still at v1. So maybe it made sense to have two packages back then?
Still, hashstructure declares an unversioned import path, while it is incompatible with packages depending on v1 (such as a package which a friend of mine is trying to work on as his first package -- no ITP yet, I haven't yet introduced him to the concept). Shouldn't then hashstructure declare a /v2 import path, and hence be renamed too? This was my reasoning when asking to drop the unversioned (v1) package.
Let me know if it makes sense! Bye :)
