[patch] always install python's eggs as unpacked files

Volodymyr Kostyrko c.kworr at gmail.com
Sun Aug 7 18:39:00 UTC 2011

07.08.2011 14:24, Andrey Zonov wrote:
> Hi,
> I've got two problems with python's eggs installed from ports.
> As you know, many eggs install from ports as archives and then
> unprivileged pseudo-user tries to use them, it's got an error about
> can't creating PYTHON_EGG_CACHE. That's OK, I've just set environment
> "PYTHON_EGG_CACHE=/var/tmp" and all works quite well. But a week ago I
> needed to run two daemons that use pymongo and I couldn't do this. The
> first daemon created PYTHON_EGG_CACHE and unpacked pymongo, but the
> second couldn't create PYTHON_EGG_CACHE because PYTHON_EGG_CACHE already
> exists! Even though they both run as "nobody".
> The second problem with that behaviour is when you're installing some
> python module from packages you need the Internet connection to get an
> egg from site and build it on-the-fly.
> Please, inspect my patch. I think that's a good solution for that problems.

I second this one, default behavior seems incorrect for me too.

I've tested the patch against devel/py-greenlet an it works for me with 
minor changes (commenting out PYDISTUTILS_INSTALLARGS).

Sphinx of black quartz judge my vow.

More information about the freebsd-ports mailing list