4 ms·
In postinst: > virtualenv /vrmd/$APP_NAME/venv This step could be skipped if you built different debs for different distro versions (in chroots for example, l
by akheron 14y ago
In postinst:
> virtualenv /vrmd/$APP_NAME/venv
This step could be skipped if you built different debs for different distro versions (in chroots for example, like sbuild does it).
Might be too much of a hassle, though, for a little gain. It just looks slightly wrong to me that you first install a deb and then go and overwrite many of the files the deb installed.
- hynek 14y agoI believe the reason is that the position of the virtualenv changes (from /home/buildbot/package-version/vrmd/venv to /vrmd/package/venv) and some links didn't match. I'm not 100% sure though, it's some time ago. :)