Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

runtimes should not live in $DOTFILES directory #5

Closed
sinewalker opened this issue Feb 8, 2017 · 3 comments
Closed

runtimes should not live in $DOTFILES directory #5

sinewalker opened this issue Feb 8, 2017 · 3 comments
Assignees
@sinewalker
Labels
enhancement
Milestone
1.0-macOS

Comments

@sinewalker
Copy link
Owner

In particular:

  • vagrant boxes should live in ~/vms/boxes in my directory structure
  • rbenv runtimes (indeed all runtimes) should live under ~/lib -- ie.e ~/lib/rbenv

Take a look at how the stuff from vendor is initialised...
@sinewalker sinewalker self-assigned this Feb 8, 2017
@sinewalker sinewalker mentioned this issue Feb 8, 2017
Closed
@sinewalker sinewalker modified the milestone: 1.0-macOS Feb 22, 2017
@sinewalker sinewalker mentioned this issue Aug 21, 2017
Closed
@sinewalker
Copy link
Owner Author

sinewalker commented Aug 21, 2017 •
edited
Loading

~/link/.vagrant.d/ has Ruby gems for Vagrant, which ought not be tracked by the repo (I'm pretty sure these are ignored...) and definitely don't belong under ~/link/

Probably the should be in ~/lib/vagrant/ if they are part of Vagrant itself

Can set $VAGRANT_HOME to this location, but will need to link the .vargant.d differently, similar to how ~/.config/ will be solved (issue #22 )

https://www.vagrantup.com/docs/other/environmental-variables.html

@sinewalker sinewalker assigned sinewalker and unassigned sinewalker Aug 22, 2017
@sinewalker sinewalker mentioned this issue Oct 14, 2017
Closed
sinewalker added a commit that referenced this issue Mar 12, 2018
@sinewalker
Link LIB files under lib/
c70c716 
This is a fairly large change that combines three things:

 * adding a Dotfiles Step to link Libs, similar to linking Configs
 * refactoring Python init/source to put VEnvs under ~/lib/python
 * Moving the vagrant library files from link/.vagrant.d to lib/vagrant

I couldn't see a way to cleanly separate all three because they relate.

There's a new global environment variable, LIB which points to the library
directory ~/lib and is used by the dotfiles Libs step, as well as by the Python
functions.

Issue #5
@sinewalker
Copy link
Owner Author

Commit c70c716 resolves.

Further libraries must use the new $LIB variable to specify a new home instead of in $HOME and be placed within Dotfiles under lib/ rather than linking under link/

@sinewalker
Copy link
Owner Author

renamed $LIB to $LIBRARY for Issue #41

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

@sinewalker sinewalker

Labels
enhancement
Projects
None yet
Milestone
1.0-macOS
Development

No branches or pull requests
1 participant
@sinewalker