You may want to consider using a type alias -- similar to how golang.org/x/net/context <https://github.com/golang/net/tree/master/context> is being transitioned to the standard library's context <https://golang.org/src/context/context.go> package.
Also, Russ Cox wrote an excellent article about codebase refactoring <https://talks.golang.org/2016/refactor.article>; I highly recommend it. On Saturday, December 2, 2017 at 7:33:06 AM UTC-8, Jonathan Hall wrote: > > I maintain an open-source Go package with a few dozen followers. ( > github.com/flimzy/kivik) > > I'm planning to transfer/rename the package to a new organization (new > package name to be: github.com/go-kivik/kivik). > > I understand that GitHub will maintain a redirect from the old location to > the new one, so in theory, old imports will continue working. > > But my question is: Are there any dangers I need to consider when making > this change, and is there anything I can do to help mitigate such dangers? > I ask mainly because I've read of some nightmares related to package > renaming (example: > https://github.com/sirupsen/logrus/issues/570#issuecomment-313933276), > and want to do everything possible to prevent such problems for my own > package. (To be clear: I don't think the Sirupsen problem in particular > will affect me, since it's not just a capitalization change). > > Keep in mind that the package has sub-packages as a dependencies (i.e. > github.com/flimzy/kivik dependson github.com/flimzy/kivik/errors), in > case this complicates things. > > Thank you, > > Jonathan > > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
