All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phil Blundell <philb@gnu.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Master broken?
Date: Tue, 05 Apr 2011 10:30:24 +0100	[thread overview]
Message-ID: <1301995824.14449.291.camel@phil-desktop> (raw)
In-Reply-To: <A24792C8-9E84-41EA-B52F-04A54FCECDF0@vanille-media.de>

On Tue, 2011-04-05 at 11:22 +0200, Dr. Michael Lauer wrote:
> Take a look at bitbake.conf The DISTRO configuration is included via the
> 'include' directive, which is a permissive include – in contrast to 'require',
> which is a mandatory include.
> 
> I don't recall our reasons for keeping it like that, but I remember that 'require'
> wasn't present at the time we wrote bitbake.conf. Perhaps we should reconsider
> that 'include'.

Partly because, as you say, bitbake didn't support "require" at the
time; and also partly because, when that part of bitbake.conf was
originally written, both DISTRO and MACHINE were much more optional than
they are today.  (In fact, the sample local.conf still implies that it's
legitimate to not select a MACHINE or DISTRO, though in practice I'm not
sure that it's feasible to get any useful results if you don't.)

I agree, it seems reasonable to change that include to a require.
Anybody who genuinely doesn't want a distro configuration is presumably
going to be savvy enough to create a dummy file in order to keep bitbake
happy.

p.





  reply	other threads:[~2011-04-05  9:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-04 14:30 Master broken? Gary Thomas
2011-04-04 14:32 ` Gary Thomas
2011-04-04 14:37   ` Sachin Kamboj
2011-04-04 14:43     ` Gary Thomas
2011-04-05  9:22       ` Dr. Michael Lauer
2011-04-05  9:30         ` Phil Blundell [this message]
2011-04-04 14:38   ` Martin Jansa
  -- strict thread matches above, loose matches on Subject: below --
2017-09-05 19:11 master broken? Leif Lindholm
2017-09-05 19:11 ` Vladimir 'phcoder' Serbinenko
2017-09-06 13:43   ` Leif Lindholm
2017-09-06 15:13     ` Vladimir 'phcoder' Serbinenko
2017-09-06 15:40       ` Leif Lindholm

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=1301995824.14449.291.camel@phil-desktop \
    --to=philb@gnu.org \
    --cc=openembedded-devel@lists.openembedded.org \
    /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.