On Wednesday 2013-08-07 09:56, Sascha Peilicke wrote:
For better or worse the guys at Google decided not to create a setup.py file and assume that everything they need is installed in the location where the main "executable" is installed.
That's not very nice of course from a packaging perspective as I think their modules should end up in site-packages and the script should live in /usr/bin.
Do you know about any Google code that does things the standard way? ;-) [...] Normally, you would add "scripts=["gcutil"]," to the setup() call to have the script wrapper installed into %_bindir. But that wouldn't work since the top-level wrapper script (from the tarball) looks at a hardcoded path and does an exec :-( FWIW, this code was written by absolute Python weenies.
There's been a study which might be related to the Google code quality. http://www.geekwire.com/2013/amazon-google-employees-ranked-least-loyal/ -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org