4 ms·
why is this necessary? shouldn't you just delete it and recreate it? installation via pip ought to take advantage of wheels and such, no?
by RodericDay 10y ago
why is this necessary? shouldn't you just delete it and recreate it?
installation via pip ought to take advantage of wheels and such, no?
- snuxoll 10y agoWould be useful for packaging up a virtualenv in an RPM (though I avoid doing that for various reasons), if there was an option to fix the paths without actually performing the move.
- meddlepal 10y agoOh god. I just went through this shit show for a .deb archives. Python is an absolute nightmare to package and distribute this way.
- Spiritus 10y agoPerhaps this is useful for you? https://github.com/spotify/dh-virtualenv https://github.com/spotify/dh-virtualenv
- meddlepal 10y agoI looked at that but didn't use it because I wanted to avoid adding yet another packaging tool into our toolbox. Instead I use virtualenv-tools and fpm. We use FPM for packaging needs and it works well enough.
- falsedan 10y agoLast time I did this, I used pip with --download on the build server, and --no-index & --find-links on the deployment target into a virtualenv in /usr/share/<package_name>. It was a pain to get the pre- & post-actions right. This still required internet access btw, but at least the deployments didn't fail when a host serving packages was unavailable.
- noisy_boy 10y agoThe machine you are installing from may not have access to internet. Then you'll need a setup to supply pip the packages. If virtualenv was truly relocatable, you can install once, push all to git and just fetch wherever you need.