- Remove unecessary $(cat)
- switch * to ./* to avoid entries with dashes to be treated as options
- replace $* with "$@"
- repeating change path serial calls - unecessary if change path is called one (get script)
* Use double quote everywhere, to avoid potential future globbing or word splitting
* Beautify EDITOR eval
* Fix typo in gvm-installer
* bin double quotes - best practice to avoid potential shell globbing and word splitting
* properly reference variable label
* simplify gvm-installer
Without this, I get this error when gvm is being loaded:
/home/manveru/.gvm/scripts/gvm-default:export:17: not an identifier: 2:/home/manveru/node_modules/.bin:/home/manveru/github/akunspy/gopbuf/bin:./node_modules/.bin:.
This links the current project into the $GOPATH/src to allow `go get` to
find the local development copy instead of the one on GitHub (or
wherever)
Signed-off-by: Dan Buch <d.buch@modcloth.com>
This commit introduces generated overlay filesystem support for
${PATH}, ${LD_LIBRARY_PATH}, and ${PKG_CONFIG_PATH} as well as
includes a working example of how to take advantage of this support
when integrating with vendored code.
While replacing pakcageset name with "--local", the packageset
information will be managed under some/local/repo/.gvm_local folder, and
add the root path of repository as the first path in GOPATH and PATH.
This makes the repository more portable since we don't store all the
go-installed package files under $HOME/.gvm .
The repository root path for gvm is definded as $PWD while
"pkgset create --local" . When "pkgset list" under some configured local
repository, it will list the root path as the first packageset, and
marked with "L".
FreeBSD does not by default install the Bourne-Again Shell (bash); and
when it is installed, it is most certainly not installed to
``/bin/bash`` due to the nuances of the conventions around local site
packages. Rather, it is installed to ``/usr/local/bin/bash``.
Golang explicitly supports FreeBSD, so it should only be reasonable for
GVM to support this target, too. As a fix, the shell script shebang
definitions now use the ``env`` tool that comes from the _coreutils_
standard package, which is installed on all conventions-adhering Linux
distributions, Mac OS X, and FreeBSD.
FreeBSD prerequisites are now listed in the documentation.
I have tested this against FreeBSD 9.0 release branch on the amd64,
and it works satisfactorily now.
Antonio Murdaca
Joshua Bussdieker
Evan Owen
Tianon Gravi
Dan Buch
Amit Gupta
jambli
Marin
Joshua B. Bussdieker
Michael Maltese
Ali Abbas
Andrei Serdeliuc
Manoj Dayaram
Michael Fellinger
Daniel Farina
Erik Aigner
Peter Souter
Dan Buch
Benjamin R. Haskell
Rafe ColtonandDan Buch
Matt T. Proud
Tatsuo Kaniwa
COLDTURNIP