On Thu, Dec 20, 2012 at 06:13:26PM -0000, Andy Doan wrote: > Andy Doan has proposed merging lp:~doanac/lava-dispatcher/config-finding-fix into lp:lava-dispatcher. > > Requested reviews: > Linaro Validation Team (linaro-validation) > > For more details, see: > https://code.launchpad.net/~doanac/lava-dispatcher/config-finding-fix/+merge/140964 > > kind of a hack, but allows us to run commands like "lava dispatch" or "lava devices" without having to source the "activate" script. > > maybe there's a better way?
Do you keep the bin/ directory of the virtualenv in your $PATH?
I don't, and added this to my bashrc:
alias init-lava='. ~/src/lava/.virtualenv/lava/bin/activate'
When I want to run lava commands I just to run `init-lava` before.
-- Antonio Terceiro Software Engineer - Linaro http://www.linaro.org
« Back to merge proposal
On Thu, Dec 20, 2012 at 06:13:26PM -0000, Andy Doan wrote: /code.launchpad .net/~doanac/ lava-dispatcher /config- finding- fix/+merge/ 140964
> Andy Doan has proposed merging lp:~doanac/lava-dispatcher/config-finding-fix into lp:lava-dispatcher.
>
> Requested reviews:
> Linaro Validation Team (linaro-validation)
>
> For more details, see:
> https:/
>
> kind of a hack, but allows us to run commands like "lava dispatch" or "lava devices" without having to source the "activate" script.
>
> maybe there's a better way?
Do you keep the bin/ directory of the virtualenv in your $PATH?
I don't, and added this to my bashrc:
alias init-lava='. ~/src/lava/ .virtualenv/ lava/bin/ activate'
When I want to run lava commands I just to run `init-lava` before.
-- www.linaro. org
Antonio Terceiro
Software Engineer - Linaro
http://