Package Details: google-appengine-go 1.9.48-1

Git Clone URL: https://aur.archlinux.org/google-appengine-go.git (read-only)
Package Base: google-appengine-go
Description: Google App Engine SDK for Go
Upstream URL: http://code.google.com/appengine/downloads.html#Google_App_Engine_SDK_for_Go
Keywords: appengine gcloud go google
Licenses: Apache
Submitter: xyproto
Maintainer: sudoforge
Last Packager: sudoforge
Votes: 32
Popularity: 0.000011
First Submitted: 2011-05-10 16:49
Last Updated: 2018-08-01 06:54

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 Next › Last »

xyproto commented on 2013-03-19 16:45

A question: Would you guys rather have the "official" names of the .py scripts in the path (and that it conflicts with the other appengine packages), or keep it like it is right now?

xyproto commented on 2013-03-19 11:47

Updated the package to 1.7.5.

xyproto commented on 2013-03-19 10:44

schultzer, I didn't notice that this package was out of date. Please use the "Flag package out-of-date" button if this should happen again in the future. Thanks.

schultzter commented on 2013-03-19 02:12

Just curious when you're going to update this to 1.7.5? They added multi-tenancy and it's something I think I need for the project I'm working on. Thanks,

xyproto commented on 2013-03-03 23:51

Yes, the name conflicts with the other appengine packages is a problem. I wish Google had a suggestion for resolving that as well. Currently, all the script files like "dev_appserver.py", in this package, has an equivivalent name like "/usr/bin/api_server-go".

Run this command for a full overview:
pacman -Ql google-appengine-go | grep usr/bin/.

schultzter commented on 2013-02-20 02:54

Something else I might suggest adding to the PKGBUILD is an entry in /etc/profile.d to put the GAE tools in the path. I did this when I maintained the SlackBuild for Slackware.

I don't know if this is the right way to do in a PKGBUILD but I added the following lines to end of the package() function:
msg2 "Creating profile.d script to add GAE commands to path..."
mkdir -p "$pkgdir/etc/profile.d"
echo "export PATH=\$PATH:/opt/$pkgname" > "$pkgdir/etc/profile.d/gae.sh"
chmod +x "$pkgdir/etc/profile.d/gae.sh"

This is suggested by Google, see http://developers.google.com/appengine/docs/go/gettingstarted/devenvironment

There's a major caveat to doing this though, the App Engine Python SDK uses the same names for their utilities but they're not compatible with the Go SDK. So if you install both you have to decide which one you want in the PATH and which one you'll call with a full path.

xyproto commented on 2013-02-16 12:17

Thanks for the fix, schultzer. Updated the package.

schultzter commented on 2013-02-16 04:19

The package only really works on 64-bit (x86_64 or amd64) systems because the fix for permissions is looking for the amd64 sub-directory.

In the PKGBUILD I replaced the line:
chmod +x "$pkgdir/opt/$pkgname/goroot/pkg/tool/linux_amd64/"*

With these lines:
if [ $CARCH != "i686" ]; then
chmod +x "$pkgdir/opt/$pkgname/goroot/pkg/tool/linux_amd64/"*
else
chmod +x "$pkgdir/opt/$pkgname/goroot/pkg/tool/linux_386/"*
fi

And then it worked on my 32-bit system.

xyproto commented on 2012-12-30 14:12

Allright, added two optional dependencies. Thanks for noticing, sinatosk.

sinatosk commented on 2012-12-27 20:06

suggestion

2 packages in the official repository

I noticed 2 warnings after starting the server

WARNING 2012-12-27 19:55:57,784 rdbms_mysqldb.py:74] The rdbms API is not available because the MySQLdb library could not be loaded.

and...

WARNING 2012-12-27 19:56:16,168 dev_appserver.py:3670] Could not initialize images API; you are likely missing the Python "PIL" module. ImportError: No module named _imaging

but after installing packages "mysql-python" and "python2-imaging"

the errors are gone

suggestion: make these 2 packages optional dependencies