[Buildroot] [PATCH] python-virtualenv: new package

Matthew Weber matthew.weber at rockwellcollins.com
Tue Mar 20 14:03:01 UTC 2018


On Sun, Feb 4, 2018 at 2:06 AM, Matthew Weber
<matthew.weber at rockwellcollins.com> wrote:
> Peter,
> On Sun, Feb 4, 2018 at 8:10 AM, Peter Korsgaard <peter at korsgaard.com> wrote:
> >>>>>> "Matt" == Matt Weber <matthew.weber at rockwellcollins.com> writes:
> >
> >  > A tool for creating a isolated python env.
> >  > Within Buildroot, the basic problem being addressed is
> >  > one of dependencies and versions, and indirectly permissions.
> >  > A great example are the Django and AMQP protocol packages.
> >  > An applications depending on these are usually locked into a specific
> >  > version.
> >
> >  > Signed-off-by: Matthew Weber <matthew.weber at rockwellcollins.com>
> >
> > Can you explain what the use case for this is? Is this to install
> > additional python packages at runtime on the target?
> >
> The main use case is to have a sandbox where you can deploy a
> configuration of python packages to support an existing application
> where you can't (reasonably) adjust all the buildroot versions of the
> similar python packages to match.  My plan is to build the main OS
> build using buildroot and then combine the existing virtualenv into
> the rootfs for deployment.  There isn't a runtime need to any dynamic
> changes to the env.

We did some prototyping and it turns out that virtualenv and
setuptools are not required to make a rehosted folder of python work
in buildroot (ie you just set a path and use it).  Note: However, on
the host machine where you gather up the folder of material, you do
need virtualenv to perform that caching activity.

I've marked my series as rejected.


More information about the buildroot mailing list