Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: yocto@yoctoproject.org, openembedded-core@lists.openembedded.org
Subject: Re: OpenEmbedded Layer Index updated
Date: Thu, 5 Sep 2013 10:04:07 +0200	[thread overview]
Message-ID: <20130905080407.GH11500@jama> (raw)
In-Reply-To: <1497435.xtb1AxO9Wj@helios>

[-- Attachment #1: Type: text/plain, Size: 989 bytes --]

On Thu, Sep 05, 2013 at 01:10:47AM +0100, Paul Eggleton wrote:
> As always, feedback is welcome.

Great job!

One more suggestion (maybe I've overlooked it):

It would be nice to be able to search recipe across all branches
(including oe-classic)

e.g. if someone asks me to include ace in our builds I would like to
just search for ace, like:
http://layers.openembedded.org/layerindex/branch/master/recipes/?q=ace

and find it's not in master/dylan/danny, but that it still is in
oe-classic
http://layers.openembedded.org/layerindex/oe-classic/recipe/13881/

Now I have to run the same search in 2-4 different branches to be sure
there isn't recipe for ace already.

In many cases we can assume that if something isn't in master then it
isn't in danny/dylan, but that's not true for e.g. mysql5 which should
correctly show availability in oe-classic/danny/dylan (and master has
mariadb).

Regards,

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

  reply	other threads:[~2013-09-05  8:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-05  0:10 OpenEmbedded Layer Index updated Paul Eggleton
2013-09-05  8:04 ` Martin Jansa [this message]
2013-09-05  8:20   ` [yocto] " 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=20130905080407.GH11500@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox