Check whether function _pw_deactivate exists before calling it.
Change-Id: If2395788cb1cee1432dbce3d752efb52d7bc4058
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/23165
Reviewed-by: Joe Ethier <jethier@google.com>
Pigweed-Auto-Submit: Rob Mohr <mohrr@google.com>
Commit-Queue: Auto-Submit <auto-submit@pigweed.google.com.iam.gserviceaccount.com>
Add deactivate steps to the environment itself and not just to the
environment folder. This means deactivate can still be run even if the
environment folder has been deleted.
Bug: 278
Change-Id: I2169d9b8c4282b97645d3c7f3385f1d9b94f0171
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/23022
Commit-Queue: Auto-Submit <auto-submit@pigweed.google.com.iam.gserviceaccount.com>
Pigweed-Auto-Submit: Rob Mohr <mohrr@google.com>
Reviewed-by: Wyatt Hepler <hepler@google.com>
Run deactivate.sh if found at the beginning of bootstrap. This should
allow shells to be reused for different projects.
Change-Id: I8af4de92b528a81c4afeb822699d2e016ffcb42f
Bug: 278
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/22580
Commit-Queue: Rob Mohr <mohrr@google.com>
Reviewed-by: Wyatt Hepler <hepler@google.com>
Change how files are passed into pw_env_setup. In most cases they're
passed in with --use-pigweed-defaults, but downstream projects now have
the option to not include Pigweed's defaults.
Change-Id: I82383705e156be14276a8498648ca376e3340efb
Bug: 274
Requires: pigweed-internal:7120
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/19380
Commit-Queue: Rob Mohr <mohrr@google.com>
Reviewed-by: Joe Ethier <jethier@google.com>
Reviewed-by: Michael Spang <spang@google.com>
