Hi all,

I've got a quick question regarding updating a Go library package after
an import name change.

I maintain golang-gopkg-pg.v5 [1], which recently has seen an update to
v6.0.0 which also changed the recommended import path from the gopkg.in
one (gopkg.in/pg.v5) to the GitHub one (github.com/go-pg/pg) [2,3]. From
my understanding of the Golang packaging approach used in the team, I
would assume that this would call for a new package for upstream version
6, namely golang-github-go-pg-pg? I realize that this would be a
duplication with two packages for the same upstream project, but given
that import names are important (and also there might be API changes so
we need to keep around the old package as a dependency) I can't see a
better way.

I wouldn't be surprised if anyone has run into that kind of issue before
and I would be thankful to hear some thoughts.

Thanks and kind regards
Sascha


[1] https://packages.qa.debian.org/g/golang-gopkg-pg.v5.html
[2]
https://github.com/go-pg/pg/commit/7d511b144d3dd20a5d6c4caf4ca6768bd04502c9
[3]
https://github.com/go-pg/pg/commit/c23ec760a20d03336e3d7f19df33af94d3e54db3


Attachment: signature.asc
Description: OpenPGP digital signature

_______________________________________________
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers

Reply via email to