It would be nice if virtualenvwrapper was updating bashrc so we can directly use all commands (workon/mkvirtualenv/...) out-of-the-box. I'm not sure how to do that in the package.yml to submit a patch.
Cheers
Description
Description
Event Timeline
Comment Actions
If you can point me to some documentation/*.yml explaining how to do that, I can take care of it myself :)
Comment Actions
Well, a package shouldn't be modifying anything in your home directory and we aren't going to patch the package when it's really an upstream issue.
Surely you can just add this to your .bashrc?
source /usr//bin/virtualenvwrapper.sh
Comment Actions
I agree with @DataDrake. Even virtualenvwrapper's install instructions tell you to do that:
https://virtualenvwrapper.readthedocs.io/en/latest/install.html#shell-startup-file
Comment Actions
I did update my bashrc but then installing the package is 100% equivalent to pip install, not sure it is relevant to keep it in the repo. I just suggested that because the deb install does it.
Comment Actions
Being available with pip is not a valid reason for removing a package from the repos.
The debian package for this abuses bash-completions to source the wrapper script. That's not an acceptable practice in Solus.