All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Design issue with the out-of-tree support
Date: Mon, 27 May 2013 21:44:19 +0200	[thread overview]
Message-ID: <51A3B793.6050409@mind.be> (raw)
In-Reply-To: <20130527211200.735491c7@skate>

On 27/05/13 21:12, Thomas Petazzoni wrote:
> Dear Arnout Vandecappelle,
>
> On Mon, 27 May 2013 18:50:54 +0200, Arnout Vandecappelle wrote:

[snip]
>>    The question is whether the OVERRIDE_SRCDIR infrastructure should apply
>> this step or not. Conceptually, it shouldn't, but that means that users
>> of OVERRIDE_SRCDIR for packages that need an autoreconf would need to do
>> the autoreconf manually. Which is probably for the best anyway, but which
>> is a change compared to current behaviour.
>
> For now, I consider doing the prepare step even on OVERRIDE_SRCDIR
> package, even if that means that we are modifying the source directory.

  Given that we've recently accepted some patches that solve problems of 
non-writeable source directories, I don't think this is appropriate. I 
think it's a valid use case to use OVERRIDE_SRCDIR to define the custom 
source of a package, which is located in some shared directory. Having 
random builds modifying that source is not appropriate.

  And now is the time to define this behaviour - changing it later can be 
considered "ABI breakage".

  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

  reply	other threads:[~2013-05-27 19:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-23 11:12 [Buildroot] Design issue with the out-of-tree support Thomas Petazzoni
2013-05-23 12:43 ` Will Wagner
2013-05-23 12:53   ` Thomas Petazzoni
2013-05-23 14:49     ` Markos Chandras
2013-05-23 18:12 ` Yann E. MORIN
2013-05-27 16:50 ` Arnout Vandecappelle
2013-05-27 19:12   ` Thomas Petazzoni
2013-05-27 19:44     ` Arnout Vandecappelle [this message]
2013-05-27 19:53       ` Thomas Petazzoni
2013-05-28 19:26         ` 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=51A3B793.6050409@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 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.