From: Richard Purdie <rpurdie@rpsys.net>
To: Paul Sokolovsky <pmiscml@gmail.com>
Cc: openembedded-devel@openembedded.org
Subject: Re: [RFC] base_less_or_equal() for numerical value testing in OE
Date: Tue, 27 Feb 2007 20:49:01 +0000 [thread overview]
Message-ID: <1172609341.28406.169.camel@localhost.localdomain> (raw)
In-Reply-To: <407130732.20070227223500@gmail.com>
On Tue, 2007-02-27 at 22:35 +0200, Paul Sokolovsky wrote:
> This code was committed, as it doesn't affect any existing aspect of
> OE. Please feel free to tweak it, and of course use!
So its not really a RFC, is it? ;-)
I think base_conditional was added but left pretty dumb since we worried
that if it was too generic it might get too many users. Inline python in
the variables hits bitbake and parsing hard and its not something I'd
like to encourage. Holger might have more specific comments. There are
usually better ways to achieve the end result in a more bitbake like
way. Also, personally I find the inline python really hard to read too.
If we are going to do it, I'd prefer to see a set functions in their own
class inherited by base.
Yes, I realise I was guilty of adding a couple of these functions with
task-base. They're mainly used in a couple of specific .bb files rather
than the core classes and hopefully their usefulness outweights any
speed penalty though...
Cheers,
Richard
next prev parent reply other threads:[~2007-02-27 20:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-27 20:35 [RFC] base_less_or_equal() for numerical value testing in OE Paul Sokolovsky
2007-02-27 20:38 ` Koen Kooi
2007-02-27 20:49 ` Paul Sokolovsky
2007-02-27 20:49 ` Richard Purdie [this message]
2007-02-27 21:31 ` Paul Sokolovsky
2007-02-27 21:40 ` Koen Kooi
2007-02-27 22:07 ` Paul Sokolovsky
2007-02-27 22:03 ` Richard Purdie
2007-03-04 23:30 ` Paul Sokolovsky
2007-03-04 23:40 ` Richard Purdie
2007-03-05 6:56 ` Koen Kooi
2007-03-05 8:12 ` Marcin Juszkiewicz
2007-03-05 10:07 ` Paul Sokolovsky
2007-03-05 9:33 ` Paul Sokolovsky
2007-02-28 13:09 ` Koen Kooi
2007-02-28 14:04 ` Philip Balister
2007-03-04 23:34 ` Paul Sokolovsky
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=1172609341.28406.169.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.org \
--cc=pmiscml@gmail.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 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.