Tim, You are not insane. I have noticed this as well w/ respect to the missing executable bit set on at least one of the goapps (and if I recall correctly, when I looked into this a month or so ago), several other scripts / binaries weren't set to executable as well, post-installation.
As you mention, I got the impression the stand-along "go SDK" was being phased out / deprecated and this was getting rolled into the cloud SDK as a module / component for it. It seems like they didn't test the new installer or something before rolling it out, and based on the combo of 1. The broken install and 2. The doublespeak of the documentation, I'd wager there is some sort of miscommunication or something between teams / departments going on right now about what's going on during this transition. I'd love to see Google actually get all their documentation updated / synced with the One True New Way and it would be good if they tried running this new installer on a few Mac OS versions to see if it actually works. Thanks, Michael On Saturday, April 8, 2017 at 8:57:29 AM UTC-7, Tim Becker wrote: > > Sorry if I'm missing something obvious, but it seems that the documenation > is very unclear about this and was just recently changed with no clear > migration instructions: > > - since recently (~ last week sometime) the prefered way to install > Golang support seems to be via the "Google Cloud SDK" (vs the "original > App > Engine SDK for Go") > - previously, the `goapp` tool was a central part of my workflow in > order to deal with the dependency on the completely outdated 1.6 version > of > Go required by appengine > - using gcloud and installing go support via `gcloud components > install app-engine-go` gets me two `goapp`s: > - ./google-cloud-sdk/platform/google_appengine/goapp > - ./google-cloud-sdk/platform/google_appengine/goroot/bin/goapp > - the first of which is a python script with no executable bit set, > and neither of which are in the PATH set up by the install.sh script > - running, eg. > `./google-cloud-sdk/platform/google_appengine/goroot/bin/goapp test` > results in the following error: > - `go: cannot find GOROOT directory: > > /private/var/folders/bs/nn10qt5j32g25qwgd77wkcyh00d7l1/T/appengine/go_appengine/goroot > > Now there are `gopath` and `goroot` dirs in the > `plattform/google_appengine` directory and I'm tempted to set the > corresponding environment variables to point to those directories, because > at least `goroot` seems to have all the necessary appengine dependencies > install in it. But this leaves me wondering, where my app should reside. > And dealing with appengine/gcloud/whatever it's called today in this manner > feels just like "trying out random stuff" > > The README contains completely outdated info from 2008. And the online > docs only seems to focus on using the "classic" SDK (e.g. > https://cloud.google.com/appengine/docs/standard/go/tools/localunittesting/ > ) > > Is there any obvious documenation that I'm missing? Am I the only person > encountering these problems? > > > (btw. I'm using OSX) > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/abb82812-08a4-4bec-af3c-4bf7bac25e58%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
