From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: ml@communistcode.co.uk
Cc: openembedded-core@lists.openembedded.org
Subject: Re: RFC: OE-Core task rework
Date: Wed, 15 Aug 2012 13:59:43 +0100 [thread overview]
Message-ID: <3038828.MQSsx4e3xZ@helios> (raw)
In-Reply-To: <502B8554.7070504@communistcode.co.uk>
On Wednesday 15 August 2012 12:17:40 Jack Mitchell wrote:
> > 1) Do we rename "task" to something a little more understandable to the
> > uninitiated, such as "package group"? The word "task" is already used in a
> > much more natural sense within bitbake as a unit of work. Historically I
> > believe we picked up this term from Debian but I'm not aware of
> > significant use by other mainstream distributions.
>
> Do the 'tasks' do anything other than specify meta-data groups? If they
> don't include any glue or additional processes then I strongly agree
> that the name should be changed.
They don't, no. Usually they are just lists of packages, although sometimes
there is some very basic logic to conditionally include/exclude some packages
based on DISTRO_FEATURES, MACHINE_FEATURES, COMBINED_FEATURES etc. or allow
substitution of default packages with others using variables.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-08-15 13:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-15 9:46 RFC: OE-Core task rework Paul Eggleton
2012-08-15 10:54 ` [yocto] " Koen Kooi
2012-08-15 12:57 ` Paul Eggleton
2012-08-15 11:17 ` Jack Mitchell
2012-08-15 12:59 ` Paul Eggleton [this message]
2012-08-15 11:25 ` Phil Blundell
2012-08-15 13:08 ` Paul Eggleton
2012-08-15 18:05 ` Mark Hatle
2012-08-15 19:12 ` Chris Larson
2012-08-15 19:30 ` Mark Hatle
2012-08-20 20:45 ` [yocto] " Mark Hatle
2012-08-21 8:49 ` Paul Eggleton
2012-08-21 8:53 ` Paul Eggleton
2012-08-21 17:34 ` Philip Balister
2012-08-28 7:05 ` Paul Eggleton
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=3038828.MQSsx4e3xZ@helios \
--to=paul.eggleton@linux.intel.com \
--cc=ml@communistcode.co.uk \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox