Global install #23

Closed
robfletcher opened this Issue Sep 28, 2012 · 10 comments

Comments

Projects
None yet
6 participants
Contributor

robfletcher commented Sep 28, 2012

It would be nice to have the option to share installations between all users of a machine (maybe with a user-specific symlink to the active version).

marc0der was assigned Sep 28, 2012

Contributor

pledbrook commented Nov 28, 2012

In a user-specified directory? Should the installation script ask where to put it? Or simply ask whether it should be a local or global install?

Another option would be for the user to set GVM_DIR before running the curl command, but that's not a common process for installation.

Owner

marc0der commented Nov 28, 2012

Yes, maybe reading it from console (with a question posed, defaulting to $HOME.gvm/).

The install script would then be doing a search/replace of @GVM_DIR@ with sed on the gvm-init.sh script on unpacking the zip.

The only problem with non-default values would be that we need to check that the user has the privileges to write for example to /usr/local.

I'll write up some scenarios first before I start any development.

bond- commented Aug 18, 2013

Any updates on this issue?

Contributor

pledbrook commented Aug 20, 2013

I think the current focus of work is converting gvm to xvm. That said, if you or anyone else could help create some Cucumber-based scenarios for this feature, that would be great. As @marcoVermeulen said, the feature needs specifying first.

Owner

marc0der commented Aug 20, 2013

Totally agree. In the meanwhile, as @pledbrook pointed out, it is possible to set the GVM_DIR environment variable in your bash profile as workaround. I tested this and it works fine.

bond- commented Aug 20, 2013

@marcoVermeulen Yes I'm doing so currently

+1 for this feature

ben3000 commented Aug 27, 2015

Try as I might, I can't get the GVM_DIR setting to work.

I set export GVM_DIR=/usr/local/gvm in ~/.bashrc. In ~/.bash_profile, I source ~/.bashrc, I delete all gvm stuff, exit the terminal, open a new one, run curl -s get.gvmtool.net | bash and it still writes everything to $HOME/.gvm.

GVM_DIR is hard-coded into the script that curl downloads, so the value I exported isn't used at all.

Owner

marc0der commented Aug 27, 2015

Working on it. Should have something out by tomorrow.

On Thu, 27 Aug 2015 at 07:15 Ben Richardson notifications@github.com
wrote:

Try as I might, I can't get the GVM_DIR setting to work.

I set export GVM_DIR=/usr/local/gvm in ~/.bashrc. In ~/.bash_profile, I source
~/.bashrc, I delete all gvm stuff, exit the terminal, open a new one, run curl
-s get.gvmtool.net | bash and it still writes everything to $HOME/.gvm.

GVM_DIR is hard-coded into the script that curl downloads, so the value I
exported isn't used at all https://stackoverflow.com/a/4609727/2495717.


Reply to this email directly or view it on GitHub
gvmtool#23 (comment).

@marc0der marc0der added a commit that referenced this issue Aug 28, 2015

@marc0der marc0der Issue #23 - Introduces ability to install locally by exporting GVM_DI…
…R before installing.
ab1a9e3

@marc0der marc0der added a commit that referenced this issue Aug 28, 2015

@marc0der marc0der Issue #23 - Introduces ability to install locally by exporting GVM_DI…
…R before installing.
9bf0afe

@marc0der marc0der added a commit that referenced this issue Aug 28, 2015

@marc0der marc0der Issue #23 - Introduces ability to install locally by exporting GVM_DI…
…R before installing.
c8f537c

@marc0der marc0der added a commit that referenced this issue Sep 16, 2015

@marc0der marc0der Issue #23 - Introduces ability to install anywhere by exporting GVM_D…
…IR before installing.

Conflicts:
	src/main/bash/install.sh
6393091

@marc0der marc0der added a commit that referenced this issue Sep 16, 2015

@marc0der marc0der Issue #23 - Adding explicit SDKMAN_DIR export to bashrc snippet.
Conflicts:
	src/main/bash/install.sh
0b47350
Owner

marc0der commented Jul 5, 2016

This has been successfully implemented.

marc0der closed this Jul 5, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment