All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 5 of 5 v2] python: allow reduced installation
Date: Thu, 17 Nov 2011 20:55:01 +0100	[thread overview]
Message-ID: <20111117205501.62cd8518@skate> (raw)
In-Reply-To: <3fb04c960d0e58ea5bb1.1321557994@devws108>

Le Thu, 17 Nov 2011 20:42:04 +0100,
Thomas De Schampheleire <patrickdepinguin+buildroot@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.

Regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2011-11-17 19:55 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-17 19:41 [Buildroot] [PATCH 0 of 5 v2] Add find utility functions / exclude files from strip / reduce python Thomas De Schampheleire
2011-11-17 19:41 ` [Buildroot] [PATCH 1 of 5 v2] Makefile.package.in: add utility functions find*clauses and notfirstword Thomas De Schampheleire
2011-11-17 19:50   ` Thomas Petazzoni
2011-11-17 20:19     ` Thomas De Schampheleire
2011-11-18  0:10   ` Arnout Vandecappelle
2011-11-18  9:41     ` Thomas De Schampheleire
2011-11-19  7:13   ` Cam Hutchison
2011-11-21  8:42     ` Thomas De Schampheleire
2011-11-17 19:41 ` [Buildroot] [PATCH 2 of 5 v2] stripping: use findfileclauses utility function Thomas De Schampheleire
2011-11-18  0:06   ` Arnout Vandecappelle
2011-11-18  1:46   ` Cam Hutchison
2011-11-18  6:21     ` Thomas De Schampheleire
2011-11-17 19:41 ` [Buildroot] [PATCH 3 of 5 v2] build: add option to exclude executables/dirs from being stripped Thomas De Schampheleire
2011-11-17 19:42 ` [Buildroot] [PATCH 4 of 5 v2] python config: move configuration into menu Thomas De Schampheleire
2011-11-17 19:42 ` [Buildroot] [PATCH 5 of 5 v2] python: allow reduced installation Thomas De Schampheleire
2011-11-17 19:55   ` Thomas Petazzoni [this message]
2011-11-18  0:24     ` Arnout Vandecappelle
2011-11-18  7:59     ` Thomas De Schampheleire

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20111117205501.62cd8518@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.