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.

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

Pushing blueprints of a new setup script #80

Open
wants to merge 29 commits into
base: master
Choose a base branch
from

Conversation

lramati
Copy link

@lramati lramati commented Aug 31, 2014

Adds 2 files:

  • setup2.py: This is the new setup script. right now its mostly functionally empty, but I tried to leave plenty of comments to explain everything and get everyone on the same page
  • setup.py.unrolled: Really just an artifact from much earlier in the process, this is just setup.py but with all the function calls taken out.

This push request is just so that other people can be aware of my work and help out with it.
I ask that this pull request not be merged until setup2.py is complete, but that instead, people push their work to my branch so that it will get added to this pull request and that when we finally merge this it will replace the old script with the new one.

Additionally, if anything is unclear, just leave a comment or include me on an issue and I'll try to clear it up.

WesleyAC and others added 29 commits January 20, 2014 23:28
…s 2 things:

1.) extend_user_env_posix writes to ~/.bashrc, not ~/.profile.  It's more widly used and doesn't require a new login, just a new virtual terminal.
2.) extend_user_env_posix will check if it needs to write to ~/.bashrc, and only write if ~/.bashrc doesn't include an export statment for the current directory.
…install, and move, their parameters, and how i think they should function. other people should now have enough to contribute to the code, although i do realize im probably missing quite a bit.
…ctions. also wrote get_dir() and rewrote get_rsp_src_dir to use it
added a comment explaining what that mysterious import is
@lramati
Copy link
Author

lramati commented Jan 20, 2015

In light of commits e09da6e and fcc3e90 I have decided that going through all the issues and IRC logs and writing a clear document explaining what everything is supposed to do should be a priority. (Also after writing 10 commits in the last 2 days, I'm tired of git lumping them in with commits from july)

@jgonggrijp jgonggrijp self-assigned this Jan 20, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants