View Single Post
Old 07-15-2015, 12:18 PM   #11
eschwartz
Ex-Helpdesk Junkie
eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.
 
eschwartz's Avatar
 
Posts: 19,421
Karma: 85400180
Join Date: Nov 2012
Location: The Beaten Path, USA, Roundworld, This Side of Infinity
Device: Kindle Touch fw5.3.7 (Wifi only)
The bootstrapper works like a charm, thanks!

The PKGBUILD automation separates source downloading from the build functions, so I am manually moving over the already-downloaded translations repo and running the separate commands, instead of bootstrapping and relying on a mandatory internet connection during the build(). I can get away with the extra lines in an automated script.
But outside of a PKGBUILD this shortcut command will be very useful (to the limited crowd that would do a source install, of course).

Thanks for clarifying the necessary steps for me.


One last, minor nit: I noticed when using a --staging-root, there will probably not be a "${staging_root}/lib/python2.7/site-packages/" directory (since python is not installed in the staging_root) so installing the environment module fails (unless it is manually created). Instead of offering a warning, shouldn't the setup create this directory?

Last edited by eschwartz; 07-15-2015 at 12:23 PM.
eschwartz is offline   Reply With Quote