Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] Support installation of Python in a different directory.
Date: Thu, 29 May 2014 11:56:02 +0200	[thread overview]
Message-ID: <20140529115602.4cc33f00@free-electrons.com> (raw)
In-Reply-To: <1401341054-16705-4-git-send-email-vomlehn@canopus-us.com>

Hello,

On Wed, 28 May 2014 22:24:14 -0700, vomlehn at canopus-us.com wrote:
> From: David VomLehn <vomlehn@canopus-us.com>
> 
> Python is both useful and large. This patch allows installation in a
> different directory, which can then be installed on its own device
> by packaging it as part of a separated filesystem.
> 
> Signed-off-by: David VomLehn <vomlehn@canopus-us.com>
> ---
>  package/python/Config.in |    7 +++++++
>  package/python/python.mk |   26 ++++++++++++++++----------
>  2 files changed, 23 insertions(+), 10 deletions(-)

The problem with this approach is that we would have to replicate this
in *all* packages. You are personally interested by changing the
installation location of Python. But I might be interested in changing
the installation location of Qt. And then the next guy the installation
location of X.org, and so on and so on.

That's a limitation of Kconfig: there is no way of creating
"properties" that would apply to all packages without creating one
option for each package. We have the same issue to define which package
should be built statically or dynamically, which package should be
built with debug symbols or not, and so on.

So I would prefer to see such advanced customization done by means of
the BR2_PACKAGE_OVERRIDE_FILE option. It would avoid cluttering the
Config.in files of packages with lots and lots of options.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2014-05-29  9:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-29  5:24 [Buildroot] [PATCH 0/3] Manage big root directory trees by breaking them up vomlehn at canopus-us.com
2014-05-29  5:24 ` [Buildroot] [PATCH 1/3] Add the capability to create sub-filesystems from the target filesystem vomlehn at canopus-us.com
2014-05-29  9:21   ` Jérôme Pouiller
2014-05-29 19:08     ` David VomLehn
2014-05-29  5:24 ` [Buildroot] [PATCH 2/3] Allow specification of values for --prefix and --exec-prefix in autotools vomlehn at canopus-us.com
2014-05-29  5:24 ` [Buildroot] [PATCH 3/3] Support installation of Python in a different directory vomlehn at canopus-us.com
2014-05-29  9:56   ` Thomas Petazzoni [this message]
2014-10-11 14:49 ` [Buildroot] [PATCH 0/3] Manage big root directory trees by breaking them up Arnout Vandecappelle

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=20140529115602.4cc33f00@free-electrons.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox