[Buildroot] [PATCH 5 of 5 v2] python: allow reduced installation

Arnout Vandecappelle arnout at mind.be
Fri Nov 18 00:24:39 UTC 2011


On Thursday 17 November 2011 19:55:01 Thomas Petazzoni wrote:
> Le Thu, 17 Nov 2011 20:42:04 +0100,
> Thomas De Schampheleire <patrickdepinguin+buildroot at gmail.com> a écrit :
> 
> > A default python installation takes more than 13M of disk space on
> > target. The python library takes about 4,5M, and the other 9M is
> > occupied by various modules in /usr/lib/python2.7. A usable
> > installation doesn't need such a large module directory. A minimal
> > configuration with only those modules needed to start an interactive
> > session requires only about 450K, plus the python library itself.
> > 
> > This patch adds an option to reduce the number of installed python
> > modules to the bare minimum. Additional modules to install can be
> > specified in the config file as a string.
> 
> While I agree that the feature is nice, I am not a fan of the
> implementation. Currently, we already have a way of enabling/disabling
> certain Python modules with one Kconfig option for each module that can
> be enabled/disabled. The list of modules that can be enabled/disabled
> this way has been built taking into account two factors :
> 
>  * We want to be able to configure out modules that have external
>    dependencies (on other libraries)
> 
>  * We want to be able to configure certain modules that take a huge
>    amount of space (I'm thinking of all the japanese/korean handling)
>    and may not be useful in most situations
> 
> So we already have a way of configuring which modules are
> built/installed with one Kconfig option per-module.
> 
> Now, you're adding a new option "I want a minimal version of Python"
> with an additional option "but I also want those additional modules". I
> think that taken together with the existing per-module Kconfig options,
> it makes the Python configuration very strange. I am not sure what to
> propose exactly (having one Kconfig option for each and every module
> would be horrible), but I don't like really much this proposal.

 Maybe a middle way is to have the reduced setup by default, with a
BR2_PACKAGE_PYTHON_EXTRA_MODULES option and another option to enable
all 'usual' modules (which would disable the EXTRA_MODULES option).
At a later stage, more options for 'usual' modules can be added.

 Regards,
 Arnout


-- 
Arnout Vandecappelle                               arnout at mind be
Senior Embedded Software Architect                 +32-16-286540
Essensium/Mind                                     http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  31BB CF53 8660 6F88 345D  54CC A836 5879 20D7 CF43



More information about the buildroot mailing list