I power my flying car with flying monkeys... I think the best answer from all this comes back to, at least for python 3, switching over to the built in venv in python3.
Other than that the symlink to a location in /usr/local for venv is another option for python 2 or packages that need to wxallowed. On the topic of pip install vs pkg_add for python pieces, this relates back to some thoughts I had about dealing with python development on FreeBSD. Let's face it things like docker exist in part because of the mess deploying python virtualenvs can become in production. I had the though of submitting an extension to iocage (my preferred jail manager, which is now written in python) so that you could basically translate a venv + pip workflow into a jail create and pkg add pyv-package type setup. However that also sounds like a big mess to maintain. Maybe something that would be more workable is something that quick translate a pip requirements.txt file into a pkg_add install script. That could work probably for any *BSD flavor. Another option is that in the scope of venv after the pkg is added through pkg_add symlinks are created in venv. I guess the only thing to figure out is what to do when a requirements file has version specifications that are incompatible with what is in the pkg system. Ken. On Tue, May 01, 2018 at 09:46:36AM -0600, Theo de Raadt wrote: > Leonid Bobrov <mazoc...@disroot.org> wrote: > > I have a plan how to completely get rid of wxallowed mount option, > > but I am not yet skilled to fix W|X ports, especially the ones > > written in C++ (I've started learning C++ recently). > > Is that like > > "I have a plan to build a flying car, but I don't > yet have any metal work skills" > > Or, aspiring to commit your life to working on world peace, from > your basement? > > Not impressive. >
