From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [RFC] meta-handheld
Date: Thu, 21 Apr 2011 20:21:20 +0100 [thread overview]
Message-ID: <1303413680.5518.359.camel@rex> (raw)
In-Reply-To: <D92FBC8F-FB70-4551-96DE-5B7AC333DB89@dominion.thruhere.net>
On Thu, 2011-04-21 at 19:27 +0200, Koen Kooi wrote:
> Op 21 apr 2011, om 18:57 heeft Graeme Gregory het volgende geschreven:
>
> > On Thu, Apr 21, 2011 at 05:04:37PM +0100, Paul Eggleton wrote:
> >> Hi all,
> >>
> >> I've discussed the possibility with a few people on IRC of creating a meta-
> >> handheld layer for support of older handheld devices - this would include
> >> Zaurus, iPAQ, SimPad, etc; possibly even EZX phones if they aren't in a layer
> >> of their own. These machines share a fair amount of commonality and I don't
> >> think that they will all survive if each one has to be put into a BSP of its
> >> own. Response so far seems to be positive but I'd like to hear thoughts from
> >> others on this.
> >>
> >> I have access to many of these devices, and this is something I am prepared to
> >> maintain on my own time, although I would appreciate help from others. I have
> >> the basis of a layer from what was left in oe-core and meta-extras but quite a
> >> lot of it would need to be brought over from OE.
> >>
> >> If people agree that this is a good idea, the next question would be where to
> >> host it - is this something that could be within the meta-oe repository?
> >>
> > Grabbing all of these barely supported machines into their own layer sounds
> > like a good plan to me.
> >
> > Id suggest just hosting it on gitorious, if its inside OE then there is the
> > magic assumption from the public that they should work (which is what happens
> > now). Then people get really dissapointed when I tell them getting it to work
> > is likely to be a hard slog.
>
> I agree with Graeme on the hosting bit. I also have all the devices you mentioned near my desk, so testing should be easy :)
I'm going to disagree, this is exactly the kind of layer fragmentation
I'd not like to see layers cause. Which website do I go to where I can
see a list of layers that exist? Who is going to maintain that list? If
its off on gitorious nobody will be able to easily find it.
The easiest solution is if git.openembedded.org or git.yoctoproject.org
can host the majority of the meta-* repositories.
Equally, I don't really see why this can't be a specific meta- group in
meta-oe. The README can clearly spell out what the expectations of the
layer are...
Cheers,
Richard
next prev parent reply other threads:[~2011-04-21 19:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-21 16:04 [RFC] meta-handheld Paul Eggleton
2011-04-21 16:57 ` Graeme Gregory
2011-04-21 17:27 ` Koen Kooi
2011-04-21 19:21 ` Richard Purdie [this message]
2011-04-22 23:09 ` Andrea Adami
2011-04-24 9:25 ` Paul Eggleton
2011-04-25 19:15 ` Khem Raj
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=1303413680.5518.359.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--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