All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>, yocto@yoctoproject.org
Subject: Re: [pull-sys940x 2/4] ranpwd: Add ranpwd recipe
Date: Fri, 10 Feb 2012 16:14:13 -0800	[thread overview]
Message-ID: <4F35B2D5.30601@linux.intel.com> (raw)
In-Reply-To: <20120207070631.GA3893@jama.jama.net>



On 02/06/2012 11:06 PM, Martin Jansa wrote:
> On Mon, Feb 06, 2012 at 03:59:36PM -0800, Joshua Lock wrote:
>> On 06/02/12 08:17, Paul Eggleton wrote:
>>> On Thursday 02 February 2012 13:11:19 Joshua Lock wrote:
>>>> Apologies. I'm wrong here. It was PRIORITY which we agreed to drop.
>>>
>>> It's worth noting however, at the same time PRIORITY removal was discussed it
>>> was acknowledged that SECTION was questionable. Logical grouping of
>>> recipes/packages is a useful thing but coming up with groupings that are
>>> meaningful in all contexts is hard :(
>>
>> Glad to know my recollection isn't wildly off the mark.
>>
>> I noticed that there are similar, yet different, SECTION values being 
>> used. If we opt to keep SECTION I wonder if we should try and 
>> standardise/sanitise it?
> 
> If there is standardised SECTION variable why not use
> recipes-${SECTION}/foo_1.0.bb as we already have couple of recipe-*
> directories and it's sometimes hard to decide to which directory
> something belongs.
> 
> Or other way around, standartise recipes-* directories and let bitbake
> decide SECTION from it (like it does for PV and PN).

Brilliant.

--
Darren

> 
> Cheers,
> 
>>
>> Debian's sections seem like reasonable inspiration? 
>> http://packages.debian.org/stable/
>>
>> I think SECTION is useful for tools like Hob and Narcissus, so I'm in 
>> favour of keeping them.
>>
>> Cheers,
>> Joshua
>> -- 
>> Joshua Lock
>>          Yocto Project "Johannes factotum"
>>          Intel Open Source Technology Centre
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
> 
> 
> 
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel


  parent reply	other threads:[~2012-02-11  0:14 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-01 22:26 [pull-sys940x 0/4][meta-intel] Inforce SYS940X BSP (Intel Atom E6xx + EG20T) Darren Hart
2012-02-01 22:26 ` [pull-sys940x 1/4] meta-intel: Add Inforce SYS940x BSP Darren Hart
2012-02-01 22:37   ` Joshua Lock
2012-02-01 23:05     ` Joshua Lock
2012-02-02 18:07       ` Darren Hart
2012-02-01 22:26 ` [pull-sys940x 2/4] ranpwd: Add ranpwd recipe Darren Hart
2012-02-01 22:40   ` Joshua Lock
2012-02-02  7:22     ` Martin Jansa
2012-02-02 18:26       ` Darren Hart
2012-02-02 19:13         ` Joshua Lock
2012-02-02 19:34           ` Darren Hart
2012-02-02 18:24     ` Darren Hart
2012-02-02 19:24       ` Joshua Lock
2012-02-02 19:32         ` Darren Hart
2012-02-02 21:11           ` Joshua Lock
2012-02-06 16:17             ` Paul Eggleton
2012-02-06 23:59               ` Joshua Lock
2012-02-07  7:06                 ` Martin Jansa
2012-02-07  9:20                   ` [yocto] " Koen Kooi
2012-02-11  0:14                   ` Darren Hart [this message]
2012-02-11  1:45                     ` Khem Raj
2012-02-01 22:26 ` [pull-sys940x 3/4] genmac: Replace RANDOM_MAC in network/interfaces with a randomly generated MAC Darren Hart
2012-02-01 22:42   ` Joshua Lock
2012-02-02 18:27     ` Darren Hart
2012-02-02 14:09   ` William Mills
2012-02-02 17:19     ` Darren Hart
2012-02-02 18:37       ` William Mills
2012-02-01 22:26 ` [pull-sys940x 4/4] netbase: Add interfaces with RANDOM_MAC for sys940x* machines Darren Hart
2012-02-01 22:52   ` Joshua Lock
2012-02-01 23:03     ` Joshua Lock
2012-02-02 18:31       ` Darren Hart
2012-02-02 19:02       ` Joshua Lock

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=4F35B2D5.30601@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=martin.jansa@gmail.com \
    --cc=paul.eggleton@linux.intel.com \
    --cc=yocto@yoctoproject.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.