which is the official(?) OE/YP openbmc layer?
colleague just yesterday asked me a couple questions about openbmc,
so i investigated the OE/YP layer, and i'm a bit confused ... the official OE layers page here:
https://layers.openembedded.org/layerindex/branch/master/layers/
refers to a meta-openbmc layer at https://github.com/facebook/openbmc,
implying it's a facebook project, but github also hosts:
can anyone clarify the relationship between those two? if there is
any?
rday
Signature · 7 lines
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================Quoted 6 lines · Robert P. J. Day
colleague just yesterday asked me a couple questions about openbmc,
so i investigated the OE/YP layer, and i'm a bit confused ... the official OE layers page here:https://layers.openembedded.org/layerindex/branch/master/layers/
Quoted 8 lines
refers to a meta-openbmc layer at https://github.com/facebook/openbmc,
implying it's a facebook project, but github also hosts:can anyone clarify the relationship between those two? if there is
any?
Oh I really hope that isn't a Google/IBM vs Facebook fork war.
I think the best way to get an answer is to email both maintainers...
Ross
Quoted 12 lines · Ross
On 21 September 2017 at 11:01, Robert P. J. Day <[email protected]> wrote:
colleague just yesterday asked me a couple questions about openbmc, so i investigated the OE/YP layer, and i'm a bit confused ... the official OE layers page here:https://layers.openembedded.org/layerindex/branch/master/layers/
refers to a meta-openbmc layer at https://github.com/facebook/openbmc,
implying it's a facebook project, but github also hosts:
Quoted 8 lines
can anyone clarify the relationship between those two? if there is any?
Oh I really hope that isn't a Google/IBM vs Facebook fork war.
I think the best way to get an answer is to email both maintainers...
after just cursory examination of both repos, i have to say, neither
of them looks particularly well-organized. or am i just being overly critical?
rday
Signature · 7 lines
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================Quoted 12 lines · Ross
On 21 September 2017 at 11:01, Robert P. J. Day <[email protected]> wrote:
colleague just yesterday asked me a couple questions about openbmc, so i investigated the OE/YP layer, and i'm a bit confused ... the official OE layers page here:https://layers.openembedded.org/layerindex/branch/master/layers/
refers to a meta-openbmc layer at https://github.com/facebook/openbmc,
implying it's a facebook project, but github also hosts:
Quoted 8 lines
can anyone clarify the relationship between those two? if there is any?
Oh I really hope that isn't a Google/IBM vs Facebook fork war.
I think the best way to get an answer is to email both maintainers...
for curiosity's sake, i spent a few minutes ignoring the apparent
facebook fork and concentrated strictly on the top-level github/openbmc content, and it seems amazingly convoluted. starting here:
i further checked out the next-level openbmc/openbmc git repo and, holy mackinaw, it contains a ton of layers.
ignoring all of the symlinked layers for regular OE/YP content
contained therein, one sees, from the top of that clone, all of the following "layer.conf" files:
$ find . -name layer.conf ./meta-phosphor/conf/layer.conf ./meta-openbmc-machines/meta-x86/meta-mellanox/conf/layer.conf ./meta-openbmc-machines/meta-x86/meta-mellanox/meta-msn/conf/layer.conf ./meta-openbmc-machines/meta-x86/conf/layer.conf ./meta-openbmc-machines/meta-x86/meta-quanta/meta-q71l/conf/layer.conf ./meta-openbmc-machines/meta-x86/meta-quanta/conf/layer.conf ./meta-openbmc-machines/meta-openpower/meta-rackspace/conf/layer.conf ./meta-openbmc-machines/meta-openpower/meta-rackspace/meta-barreleye/conf/layer.conf ./meta-openbmc-machines/meta-openpower/conf/layer.conf ./meta-openbmc-machines/meta-openpower/meta-ingrasys/conf/layer.conf ./meta-openbmc-machines/meta-openpower/meta-ingrasys/meta-zaius/conf/layer.conf ./meta-openbmc-machines/meta-openpower/meta-ibm/meta-garrison/conf/layer.conf ./meta-openbmc-machines/meta-openpower/meta-ibm/meta-firestone/conf/layer.conf ./meta-openbmc-machines/meta-openpower/meta-ibm/meta-romulus/conf/layer.conf ./meta-openbmc-machines/meta-openpower/meta-ibm/conf/layer.conf ./meta-openbmc-machines/meta-openpower/meta-ibm/meta-palmetto/conf/layer.conf ./meta-openbmc-machines/meta-openpower/meta-ibm/meta-witherspoon/conf/layer.conf ./meta-openbmc-machines/meta-evb/conf/layer.conf ./meta-openbmc-machines/meta-evb/meta-evb-aspeed/conf/layer.conf ./meta-openbmc-machines/meta-evb/meta-evb-aspeed/meta-evb-ast2500/conf/layer.conf ./meta-openbmc-bsp/meta-aspeed/conf/layer.conf ./meta-openbmc-bsp/meta-aspeed/meta-ast2500/conf/layer.conf ./meta-openbmc-bsp/meta-aspeed/meta-ast2400/conf/layer.conf $
not only does that single "git clone" apparently contain 23
individual layers, some of the content represents independent projects in github. for example:
openbmc/meta-aspeed <==> openbmc/openbmc/meta-openbmc-bsp/meta-aspeed
same with meta-openpower, possibly others.
sorry to pollute this ML with questions about a specific layer, i
just figured it would be a piece of cake to take a look at this stuff for a colleague and it got ugly in a hurry.
i'll check in with the actual maintainers, but if anyone out there
is doing current work with openbmc, any pointers as to the current state of that content would be appreciated.
rday
Signature · 7 lines
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================