Re: [go-nuts] What's the best way to maintain a package repository that have the major version in the import path?

On Thursday, February 22, 2018 at 6:43:07 AM UTC-5, alex@gmail.com wrote: > > Yup, the package I'm working on really cannot have 2 instances even in > different import paths as it deals with a shared resource and code that > must be run on the main thread. > So I have to choose between

Re: [go-nuts] What's the best way to maintain a package repository that have the major version in the import path?

On Thu, Feb 22, 2018 at 10:27 PM wrote: > On Thursday, February 22, 2018 at 9:53:20 PM UTC+8, Axel Wagner wrote: >> >> Daisy chaining would mean I would only have to code API translations for >>> the latest API but then it's debug hell and if one version in the chain >>>

Re: [go-nuts] What's the best way to maintain a package repository that have the major version in the import path?

On Thursday, February 22, 2018 at 9:53:20 PM UTC+8, Axel Wagner wrote: > > Daisy chaining would mean I would only have to code API translations for >> the latest API but then it's debug hell and if one version in the chain >> breaks, >> it means fixing all the newer versions. Also there's a

Re: [go-nuts] What's the best way to maintain a package repository that have the major version in the import path?

On Thu, Feb 22, 2018, 12:43 wrote: > On Thursday, February 22, 2018 at 5:29:23 PM UTC+8, Axel Wagner wrote: >> >> Have you read https://research.swtch.com/vgo-import? It talks about >> singletons and also how to solve that with different import paths. >> Note, that this is

Re: [go-nuts] What's the best way to maintain a package repository that have the major version in the import path?

On Thursday, February 22, 2018 at 5:29:23 PM UTC+8, Axel Wagner wrote: > > Have you read https://research.swtch.com/vgo-import? It talks about > singletons and also how to solve that with different import paths. > Note, that this is also independent of *how* the different import paths > are

Re: [go-nuts] What's the best way to maintain a package repository that have the major version in the import path?

On Thu, Feb 22, 2018 at 7:18 AM wrote: > I don't think changing the module name would be a good idea for singletons > tho. > Have you read https://research.swtch.com/vgo-import? It talks about singletons and also how to solve that with different import paths. Note, that

Re: [go-nuts] What's the best way to maintain a package repository that have the major version in the import path?

I don't think changing the module name would be a good idea for singletons tho. And having a v0 has the added benefit of using newer codes while maintaining backwards compatible API. So no more backporting and all the mess of having multiple branches. On Thursday, February 22, 2018 at 1:49:53

Re: [go-nuts] What's the best way to maintain a package repository that have the major version in the import path?

On Wed, Feb 21, 2018, at 22:35, alex.rou...@gmail.com wrote: > vgo suggested that package developers put the major version into the import > path e.g. foo/v1. > However dealing with a VCS like git, this thought occur to me, what would > it look like when the project needs to move from v1 to v2?