From: Tomas Frydrych <tf+lists.yocto@r-finger.com>
To: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: [poky] RaspberryPi Layer
Date: Mon, 21 May 2012 11:12:51 +0100 [thread overview]
Message-ID: <4FBA1523.30307@r-finger.com> (raw)
In-Reply-To: <CAK18fxHoxdznsSbeSybm3QAym-YQa=_fzsMgOr2QHqFUH5ygiw@mail.gmail.com>
Hi,
On 21/05/12 09:47, Andrei Gherzan wrote:
> There are issues that cannot be solved with just one layer. A distro is
> a workaround but still. More about this, rpi layer will be included in
> yocto project repos as Richard plans so it makes sense to have a yocto
> specific layer. It could be a discussion here about using a core layer
> and above that some distro specific layers but in my opinion this would
> be a little too complicated for this. Right now i use a distro file
> which inherits poky distro in order to BBMASK some bbappends which we
> don't have in poky. Clear now?
This really needs to be a BSP layer, not a distro, so that people can
build a custom distros with it; i.e., the fact that you currently BBMASK
packages in the BSP configuration means it will not be useable as an
independent layer.
> > Until a stable version of this layer we will keep this layer on
> > bitbucket: https://bitbucket.org/agherzan/meta-raspberrypi.
>
> Considering that John Willis's work is on github, where a number of
> people follow it already, why move this somewhere else? This just makes
> it harder for anyone interested in this work to track what is going on.
>
>
> I'm not a github user. But this wouldn't be a problem. I find bitbucket
> a better place to hold any kind of git repo: it has collaborative
> options, you can have private repos (free) and a bunch of other stuff.
> And after all it is a git. You can clone it, fetch and pull anywhere on
> your computer. So i don't find this a problem.
It should be easy for people interested in the m-rpi effort to track
what is happening, splitting it over multiple online services does
facilitate that; more so it implicitly turns this into two separate
projects simply because someone wanting to contribute will have to
choose where to send the contributions to.
Tomas
next prev parent reply other threads:[~2012-05-21 10:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-19 21:51 RaspberryPi Layer Andrei Gherzan
2012-05-19 21:51 ` Andrei Gherzan
2012-05-19 22:09 ` Chris Tapp
2012-05-21 7:47 ` [poky] " Tomas Frydrych
2012-05-21 8:47 ` Andrei Gherzan
2012-05-21 9:19 ` Paul Eggleton
2012-05-21 9:25 ` Andrei Gherzan
2012-05-21 9:32 ` Paul Eggleton
2012-05-21 15:16 ` John Willis
2012-05-21 15:31 ` Paul Eggleton
2012-05-21 15:34 ` John Willis
2012-05-21 15:41 ` Gary Thomas
2012-05-21 15:45 ` Andrei Gherzan
2012-05-21 16:21 ` Tomas Frydrych
2012-05-21 10:12 ` Tomas Frydrych [this message]
2012-05-21 19:59 ` Chris Tapp
2012-05-21 20:08 ` Andrei Gherzan
2012-05-22 19:40 ` Chris Tapp
2012-05-22 19:43 ` Andrei Gherzan
2012-05-22 21:46 ` 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=4FBA1523.30307@r-finger.com \
--to=tf+lists.yocto@r-finger.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.