Skip to content
This repository has been archived by the owner on May 19, 2023. It is now read-only.

Change how .bash_profile is updated #58

Open
wants to merge 7 commits into
base: python
Choose a base branch
from

Conversation

embray
Copy link
Contributor

@embray embray commented Aug 15, 2016

Now, instead of writing all our configuration directly into .bash_profile we write a "default" bash_profile in ~/.swc/etc/bash_profile which is sourced from the user's actual ~/.bash_profile. This makes it easier to keep all the Software Carpentry-specific configuration in one place, and to update and enable/disable it more easily.

This PR builds on top of #57 but could be made to work independently as well.

embray and others added 7 commits August 4, 2016 16:03
to aid in using it for building an (eventual) offline installer.

 * -d sets the directory to "install" to, instead of ~/.swc
 * --no-update-profile prevents the script from tampering with
   .bash_profile
 * --no-update-nanorc prevents installing the "nano.rc" file
   in ~
…ies into the target install_directory.

Should probably add the same to zip_install as well.
…nstalling the nano.rc file itself into separate steps. Update the --no-update-nanorc to only exclude the latter (but still install the syntax files). Also make use of the new 'include' argument to tar_install to *only* install the syntax files and not the rest of the source code, which is not used.
the actual Software Carpentry configuration.  This makes it easier
to update the config, and easier for the user to enable/disable
our configuration without it leaving a mess of things in their
actual .bash_profile.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant