From: Frans Meulenbroeks <fransmeulenbroeks@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] meta-openembedded layer for yocto hosted on oe.org
Date: Mon, 20 Dec 2010 18:16:49 +0100 [thread overview]
Message-ID: <AANLkTiks4PYZxZCQgsprveY1jNQgpy_mMVTOwg3DtsqX@mail.gmail.com> (raw)
In-Reply-To: <4D0F8AB7.1020104@xora.org.uk>
Nice piece of work & a good plan but...
Who will be the owners/maintainers of the layers?
I maintain several multimedia recipes (mythtv with all that is dragged
in (which is a.o. a lot of perl stuff), various cd* related recipes,
python-coherence and the python stuff it uses, mediatomb, and it seems
recently people seem to see me as the first line of contact if they
have musicpd issues), as well as some file sharing recipes.
Any idea on how I get them added, and how to deal with updates for these?
An alternate approach would be to let the stuff live in poky-extras.
See this proposal from RP:
http://www.mail-archive.com/yocto@yoctoproject.org/msg00286.html
Frans.
PS: personally I would have preferred it if console-image was in the
common part.I guess some other recipes will get fairly identical
recipes.
Maybe we should have a generic console-image and let each distro use
.bbappend or aminc to extend on it.
next prev parent reply other threads:[~2010-12-20 17:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-20 15:53 [RFC] meta-openembedded layer for yocto hosted on oe.org Koen Kooi
2010-12-20 16:56 ` Graeme Gregory
2010-12-20 17:16 ` Frans Meulenbroeks [this message]
2010-12-20 19:25 ` Maupin, Chase
2010-12-20 20:31 ` Frans Meulenbroeks
2010-12-21 8:16 ` Koen Kooi
2010-12-21 17:51 ` Frans Meulenbroeks
2010-12-21 18:41 ` Khem Raj
2010-12-21 20:28 ` Marcin Juszkiewicz
2010-12-21 21:16 ` Frans Meulenbroeks
2011-01-02 11:29 ` Frans Meulenbroeks
2010-12-22 5:43 ` Esben Haabendal
2010-12-21 9:45 ` Khem Raj
2010-12-21 18:48 ` Tom Rini
2010-12-21 19:25 ` Cliff Brake
2010-12-21 20:39 ` Chris Larson
2010-12-21 15:43 ` Cliff Brake
2010-12-21 16:25 ` Koen Kooi
2010-12-21 21:03 ` Denys Dmytriyenko
2010-12-22 11:19 ` Koen Kooi
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=AANLkTiks4PYZxZCQgsprveY1jNQgpy_mMVTOwg3DtsqX@mail.gmail.com \
--to=fransmeulenbroeks@gmail.com \
--cc=openembedded-devel@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.