Hi Sascha,
On 27/03/17 11:14, Sascha Steinbiss wrote:
> 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
Ugh. Another upstream dropping gopkg.in.. Sadly some upstreams found the
service to unreliable and so they went back to github import paths, but
losing in the way the ability to have API versioning.
Maybe a good idea would be to ask upstream what do they plan to do
regarding API changes. This is becoming a bigger and bigger issue in
golang, but the community seems blind to it. I would try to convince
them to keep the semantic versioning, but that is probably not easy to do..
> 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.
If there is an api change and there are packages depending on v5, you
can't remove the old package. For the new one.. it is a mess, but we
basically depend on what upstream plans to do, and we might need to go
with the new naming format. If they do a v7 in the future without
changing the import path, then we will have to create a new source
package and leave the old one just for compatibility.
--
Martín Ferrari (Tincho)
___
Pkg-go-maintainers mailing list
Pkg-go-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
