From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/3] Manage big root directory trees by breaking them up.
Date: Sat, 11 Oct 2014 16:49:22 +0200 [thread overview]
Message-ID: <54394372.30604@mind.be> (raw)
In-Reply-To: <1401341054-16705-1-git-send-email-vomlehn@canopus-us.com>
On 29/05/14 07:24, vomlehn at canopus-us.com wrote:
> From: David VomLehn <vomlehn@canopus-us.com>
Hi David,
We've discussed this series at the Buildroot developer meeting, and we decided
to reject it. This is why:
> These patches are not as tightly coupled as the usually series of patches,
> but I think the pieces make more sense when viewed in the context of the
> whole patchset. The problem to be solved is that Python is big and my root
> filesystem has to fit in a little flash device. So, I:
>
> 1. Created the ability to break the target filesystem into multiple
> filesystems,
Although we do want to support the possibility to break down the target
filesystem into partitions, we don't want to add so many config options to do
it. Basically, we want to keep buildroot as simple as possible. So instead, we
want to provide the tools that are required to do this, like genpart, and then
allow the user to do it in a post-build and post-image script.
> 2. Enhanced autotools so that I could specify the --prefix and
> --exec-prefix values. This allowed me to install packages in
> their own directory, which the above patch lets me split into a
> filesystem I can store on a much bigger flash device, and
> 3. I modified the Python package so that the installation directory
> is a configurable.
The problem with this is that it adds a user-visible feature that is only
useful for autotools packages. It is a bit similar to FOO_OVERRIDE_SRCDIR, but
for that one we can guarantee that it works for all packages. The CONF_PREFIX
only works for autotools packages and for python, we would need many many more
changes to have it for all possible packages.
In addition, this is something that will break down easily, because it is not
tested. E.g. if a .mk file installs 10 files, and we forget to add the
CONF_PREFIX for one of them, that's easy to miss.
Therefore we decided to reject these two patches as well.
That said, thank you for your contribution and thank you for using buildroot!
Regards,
Arnout
[snip]
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
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: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
prev parent reply other threads:[~2014-10-11 14:49 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
2014-10-11 14:49 ` Arnout Vandecappelle [this message]
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=54394372.30604@mind.be \
--to=arnout@mind.be \
--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