Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/2] base: improve PACKAGECONFIG handling logic
Date: Tue, 10 Sep 2013 20:49:00 +0200	[thread overview]
Message-ID: <20130910184900.GU11500@jama> (raw)
In-Reply-To: <CAJTo0LaiEfUqXXz5UtaGzfFU2q1try_MHgbrUUViZcz=4jUXoA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1469 bytes --]

On Tue, Sep 10, 2013 at 06:17:27PM +0100, Burton, Ross wrote:
> On 10 September 2013 18:15, Ross Burton <ross.burton@intel.com> wrote:
> > -                if num >= 3 and items[2]:
> > -                    extradeps.append(items[2])
> > -                if num >= 4 and items[3]:
> > -                    extrardeps.append(items[3])
> > -                if num >= 1 and items[0]:
> > -                    extraconf.append(items[0])
> > +                if items:
> > +                    extraconf.append(items.pop(0))
> > +                # Skip over disable
> > +                if items:
> > +                    items.pop(0)
> > +                if items:
> > +                    extradeps.append(items.pop(0))
> > +                if items:
> > +                    extrardeps.append(items.pop(0))
> 
> I should note that in a PACKAGECONFIG[foo] such as ",,,foo" this will
> add some whitespace to EXTRA_OECONF and DEPENDS.  If this is a massive
> concern I can sort it, but the clear code trumps the odd extra
> whitespace in my mind.

EXTRA_OECONF/DEPENDS space will probably force do_compile/do_install
tasks to execute again, while RDEPENDS/RRECOMMENDS only PACKAGECONFIGs
could be enabled with only do_package re-executed.

I don't know how many PACKAGECONFIG options we have without first 3
parameters, but in your example with foo it would be significant change.

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

  reply	other threads:[~2013-09-10 18:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-10 17:15 [PATCH 1/2] base: improve PACKAGECONFIG handling logic Ross Burton
2013-09-10 17:15 ` [PATCH 2/2] base: add RRECOMMENDS to PACKAGECONFIG Ross Burton
2013-09-10 17:17 ` [PATCH 1/2] base: improve PACKAGECONFIG handling logic Burton, Ross
2013-09-10 18:49   ` Martin Jansa [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-09-11 18:17 Ross Burton
2013-09-12  3:30 ` Saul Wold

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=20130910184900.GU11500@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    /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