Is the gb project dead?

[mbsulliv]

There haven't been any updates since May 11, 2017. What's going on?

[davecheney]

Sorry I have a day job and not much free time to work on open source. I hope to have more time towards the end of the year.

…

On 8 Apr 2018, at 16:24, Michael Sullivan ***@***.***> wrote: There haven't been any updates since May 11, 2017. What's going on? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[joyhope]

Is the issue #733 difficult to process? I hope to use gb with the latest golang.

[m00sey]

First of all, I'll say over the 2+ years of using gb/gb vendor, it has been invaluable. So thank you @davecheney

Given the latest changes to go build/test in go 1.10 (https://golang.org/cmd/go/#hdr-Build_and_test_caching) and the introduction of dep (https://golang.github.io/dep/) we will be moving away from gb, and back inline with the go way.

While I appreciate our use case does not cover everything gb offers, build caching and dependency management were the main two. Not to take anything away from gb though, it filled a big void for us, for a long time.

[davecheney]

Thank you for your kind words. There are two factors at play. The first is time, there’s only so much of it and i haven’t had any to work on my open source projects for well over a year because they remain a hobby. Th second, and more important, is that with the acknowledgement of the problem by ththe go team with vgo to continue to push gb as a viable solution would be detrimental to the goal of the whole Go community just settling on one damn tool and moving on. With that said, I use gb for my personal projects and will continue to maintain it, but right now I have less than zero time to do that.

…

On 20 Apr 2018, at 05:31, Kevin Griffin ***@***.***> wrote: First of all, I'll say over the 2+ years of using gb/gb vendor, it has been invaluable. So thank you @davecheney Given the latest changes to go build/test in go 1.10 (https://golang.org/cmd/go/#hdr-Build_and_test_caching) and the introduction of dep (https://golang.github.io/dep/) we will be moving away from gb, and back inline with the go way. While I appreciate our use case does not cover everything gb offers, build caching and dependency management were the main two. Not to take anything away from gb though, it filled a big void for us, for a long time. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[txchen]

@m00sey I really like the fact that when I use gb, I don't have to put my repo in $GOPATH and having an ugly long path.
So if you move to use dep, can this still be the case?

[m00sey]

Without knowing your usage for gb, I can only say, dep merely requires you have a $GOBIN defined and dep installed, it will vendor dependencies under the src directory it is run from.

For your particular usage check https://golang.github.io/dep/docs/new-project.html it goes over the various scenarios for dep.

[txchen]

Thanks @m00sey ! Seems still no way to place the repo outside GOPATH, this is a bummer.

[julik]

I do side with @txchen on this one. gb has been invaluable for us as well and also specifically for the use case of not having to put things on the $GOPATH - since not everybody uses this usage pattern, and some (myself included) find it a questionable invention. So with dep becoming the dependency manager by default I woulds till appreciate gb helping the "not everybody works as if they had company crossmounts on Plan9" way. A ton.

And of course @davecheney thank you for gb because it literally the thing that prevented me from quitting Go completely.

[mouse07410]

@davecheney I understand you're busy. You're probably aware of the change in go made last December (see golang/go#30784 (comment)).

What is necessary to bring gb in sync with go? Would you be able to do that? Is it just a matter of some small edits and recompile, or the change likely to be significant?

Thanks! (And not counting this problem, which makes it impossible to use gb with the currently released go, gb is a nice tool - I'm happy that it's around.)

[davecheney]

I'm hoping i'll have some time in the second half of the year to work on gb. I'm sorry, i'm perpetually spread too thin.

[mouse07410]

Understood, thanks. Maybe in the meanwhile you can tell how I can accomplish results of "gb build" using only "go" tool? Assuming that "gb" invokes "go" under the hood?

[davecheney]

Understood, thanks. Maybe in the meanwhile you can tell how I can accomplish results of "gb build" using only "go" tool?

I'm not sure. I'm sorry I wish I had time to help but I'm at 300% capacity.

Assuming that "gb" invokes "go" under the hood?

gb is not a wrapper around the go tool.

[jpeeck-spring]

@davecheney adding on to the theme is it dead? I just wanted to let you know that apparently getgb.io is for sale and not registered to your website anymore.

We use gb on an older project of ours which I'm just getting into and just noticed that the URL doesn't work anymore.

Also I know how tough it is to balance day job + a side project, so thanks for doing this - not complaining here, just trying to bring this to your attention, incase you didn't know!

[davecheney]

At the moment I don’t have any time to work on any of my side projects, I’m sorry.

…

On 4 Sep 2019, at 17:40, Jonas Peeck ***@***.***> wrote: @davecheney adding on to the theme is it dead? I just wanted to let you know that apparently getgb.io is for sale and not registered to your website anymore. We use gb on an older project of ours which I'm just getting into and just noticed that the URL doesn't work anymore. Also I know how tough it is to balance day job + a side project, so thanks for doing this - not complaining here, just trying to bring this to your attention, incase you didn't know! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[jpeeck-spring]

I completely understand your situation and I don't think you have to apologize for that :)
Thanks for the quick feedback - I just wanted to let you know about your domain is all!