Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 3/4] tar: upgrade to v1.26
Date: Mon, 6 Jun 2011 07:09:32 -0500	[thread overview]
Message-ID: <4DECC37C.2010003@windriver.com> (raw)
In-Reply-To: <1307357181.7672.3.camel@rex>

On 6/6/11 5:46 AM, Richard Purdie wrote:
> On Mon, 2011-06-06 at 09:00 +0100, Phil Blundell wrote:
>> On Sun, 2011-06-05 at 21:49 -0700, Scott Garman wrote:
>>>  SECTION = "base"
>>> +PRIORITY = "optional"
>>
>> Seeing this sort of thing makes me wonder whether SECTION and PRIORITY
>> actually belong in the core metadata at all.  It seems as though the
>> determination of what exactly is "standard" vs "optional" is a matter of
>> distro policy and this would be better done in the distro config files.
>>
>> Also, just on a pragmatic issue, the two values above are actually what
>> bitbake.conf sets as default anyway so there isn't much to be gained by
>> specifying them in the recipe as well.
> 
> I have to admit I keep wondering about these.
> 
> PRIORITY does seem a bit of a pointless variable in the default metadata
> and I'm borderline in favour of dropping it and leaving it to any
> distros who want to use it, maybe sharing an include file.

I agree as well, PRIORITY seems a bit iffy at this point.

> SECTION does at least start to become useful in an image generation UI
> as a way to group packages roughly by type which makes me think it has a
> good default usecase (and OE-Core did clean up the values of it to at
> least be consistent).

I think the value of SECTION needs to remain.  It's being used to group the
packages (as Richard mentions...)

Just my 2-cents.

--Mark

> Cheers,
> 
> Richard
> 
> 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core




  reply	other threads:[~2011-06-06 12:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-06  4:49 [PATCH 0/4] Recipe upgrades: openssh, grep, tar Scott Garman
2011-06-06  4:49 ` [PATCH 1/4] openssh: upgrade to v5.8p2 Scott Garman
2011-06-06  4:49 ` [PATCH 2/4] grep: upgrade to v2.8 Scott Garman
2011-06-06  4:49 ` [PATCH 3/4] tar: upgrade to v1.26 Scott Garman
2011-06-06  8:00   ` Phil Blundell
2011-06-06 10:46     ` Richard Purdie
2011-06-06 12:09       ` Mark Hatle [this message]
2011-06-07  8:24         ` Phil Blundell
2011-06-06  4:49 ` [PATCH 4/4] distro-tracking: update openssh, tar, and grep Scott Garman
2011-06-08 16:51 ` [PATCH 0/4] Recipe upgrades: openssh, grep, tar 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=4DECC37C.2010003@windriver.com \
    --to=mark.hatle@windriver.com \
    --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