-
Notifications
You must be signed in to change notification settings - Fork 36
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.
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
Getting rid of the "machines" folder.. #40
Comments
I will suggest some variant over a theme like this:
|
I think Roberts plan sounds good. My only input on this was that SurfCat could use a git submodule for machines. That way there would be a link between the PyExpLabSys source code and updates there and the machines repo. But, if you are going for a true separation, like what Robert is hintint at, which I think is better, then there is no need for this. The bottom line is that it would be give you a slightly simpler setup and update, but at the expense of using the the semi-magical git submodules during development, so not worth it IMO. |
Great, I will suggest that @Ejler initiate the work of making a stand-alone machines folder for surfcat. If you want to preserve git-history, you could fork and remove everything else, or you could simply copy the files and start a new repo. |
Sounds great. I'm on it. |
If PyExpLabSys is installed with pip --user, should I then update bootstrap to also user --user in the pip step? |
@robertjensen The need not to hose ones system dirs is of course smaller on RPi's, but still, I'm surprised it wasn't already, and since it is always the same user, that totally makes sense to me |
The machines folder is great for inspirational scripts, but horrible in terms of sharing PyExpLabSys between different "installations".
Ideas to separate machines from PyExpLabSys?
The text was updated successfully, but these errors were encountered: