All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jack Mitchell <ml@communistcode.co.uk>
To: openembedded-core@lists.openembedded.org
Subject: Re: RFC: OE-Core task rework
Date: Wed, 15 Aug 2012 12:17:40 +0100	[thread overview]
Message-ID: <502B8554.7070504@communistcode.co.uk> (raw)
In-Reply-To: <2404459.dJBf5OQotX@helios>

On 15/08/12 10:46, Paul Eggleton wrote:
> Hi all,
>
> There have been a few requests to review the task recipes (i.e. package
> groups) provided by OE-Core, and indeed these have not really been looked at
> seriously since OE-Core was created. Ideally I think we want them to be useful
> to a wide audience and provide useful units of functionality that can be added
> to an image without the person doing the selection having to manually select
> too many individual packages. Imagine presenting the list of tasks to someone
> in a UI for assembling images (such as Hob or Narcissus) and you can start to
> see that we have some work to do in this area.
>
> I know various distros and users of OE-Core have created their own tasks or
> resurrected tasks from OE-Classic, and this is an opportunity to perhaps look
> at bringing some of these (or at least, parts of them) into the core. It is
> true that tasks will often be an expression of distro policy, and we also
> can't have any tasks in OE-Core that refer to packages that don't exist in OE-
> Core; thus distros will always be extending the base tasks or adding their own
> - and that's fine. However, with some thought I believe we can come up with a
> set of tasks that are generally useful to most people using OE-Core.
>
> For reference, I've compiled a list on the wiki of the current tasks in OE-
> Core with links to the recipes and some notes:
>
>    http://www.openembedded.org/wiki/OE-Core_Task_Rework
>
> Some of the things I think we ought to consider/address as part of this
> exercise:
>
> 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.

-- 

   Jack Mitchell (jack@embed.me.uk)
   Embedded Systems Engineer
   http://www.embed.me.uk

--




  parent reply	other threads:[~2012-08-15 11:28 UTC|newest]

Thread overview: 25+ 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 10:54   ` Koen Kooi
2012-08-15 12:57   ` [yocto] " Paul Eggleton
2012-08-15 12:57     ` Paul Eggleton
2012-08-15 11:17 ` Jack Mitchell [this message]
2012-08-15 12:59   ` Paul Eggleton
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-15 18:01 ` Mark Hatle
2012-08-15 19:15   ` Chris Larson
2012-08-20 20:45 ` [yocto] " Mark Hatle
2012-08-20 20:45   ` Mark Hatle
2012-08-21  8:49   ` [yocto] " Paul Eggleton
2012-08-21  8:49     ` Paul Eggleton
2012-08-21  8:53     ` [yocto] " Paul Eggleton
2012-08-21  8:53       ` Paul Eggleton
2012-08-21 17:34     ` [yocto] " Philip Balister
2012-08-21 17:34       ` [OE-core] " Philip Balister
2012-08-21 17:34       ` [OE-core] [yocto] " Philip Balister
2012-08-28  7:05 ` Paul Eggleton
2012-08-28  7:05   ` [OE-core] " 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=502B8554.7070504@communistcode.co.uk \
    --to=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 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.