From: Phil Blundell <philb@gnu.org>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: OE-core <openembedded-core@lists.openembedded.org>,
OE-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [RFC] OpenGL packaging/staging policy
Date: Mon, 22 Oct 2012 20:25:37 +0100 [thread overview]
Message-ID: <1350933937.6763.10.camel@x121e.pbcl.net> (raw)
In-Reply-To: <CAP9ODKrMoEJMXWNa0rx0KyQjx3hJhFzPOJCH+eDYqiDm3saMxg@mail.gmail.com>
On Mon, 2012-10-22 at 15:33 -0200, Otavio Salvador wrote:
> On Mon, Oct 22, 2012 at 2:35 PM, Burton, Ross <ross.burton@intel.com> wrote:
> ...
> > Rule 1. Unambiguous package naming
> >
> > Debian-style renaming and multiple providers of the same API doesn't
> > work as you'll end up with multiple packages in the same feed called
> > libgl1, so all GL packages should be named in the style of libgl-foo,
> > where foo is the source of the package. I've got a branch where this
> > is implemented for Mesa as a proof of concept[1], and the Python
> > fragment could easily be moved into a class and re-used easily.
>
> It would be nice to also have a common SoC arch so the binaries are
> clear not allarch but not rebuild for every board.
>
> For example in iMX53 and iMX51 case they share same GL package set and
> we could have a armv7-imx5 or so common to all them so we'd not
> rebuild it for every board.
Surely in the case Ross describes, the "imx5" bit would be encoded into
the package name (i.e. they'd be libgl-imx5) and then PACKAGE_ARCH can
just be used as normal to represent the ISA and/or ABI. I can't think
of any situation where encoding the GPU type into PACKAGE_ARCH would be
especially useful.
p.
next prev parent reply other threads:[~2012-10-22 19:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-22 16:35 [RFC] OpenGL packaging/staging policy Burton, Ross
2012-10-22 17:19 ` Tomas Frydrych
2012-10-22 19:27 ` Burton, Ross
2012-10-22 20:25 ` Tomas Frydrych
2012-10-23 2:06 ` Daniel Stone
2012-10-23 8:37 ` Tomas Frydrych
2012-10-23 9:18 ` Daniel Stone
2012-10-23 9:49 ` Tomas Frydrych
2012-10-29 17:26 ` Burton, Ross
2012-10-29 18:27 ` Tomas Frydrych
2012-11-20 16:52 ` Burton, Ross
2012-10-22 17:32 ` [oe] " Phil Blundell
2012-10-22 17:38 ` Otavio Salvador
2012-10-22 19:26 ` Burton, Ross
2012-10-22 17:33 ` Otavio Salvador
2012-10-22 19:25 ` Phil Blundell [this message]
2012-10-22 17:37 ` Mark Hatle
2012-10-22 19:29 ` Burton, Ross
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=1350933937.6763.10.camel@x121e.pbcl.net \
--to=philb@gnu.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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