4 ms·
Would 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 actuall
by snuxoll 10y ago
Would 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.