All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David Nyström" <david.nystrom@enea.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: "meta-virtualization@yoctoproject.org"
	<meta-virtualization@yoctoproject.org>,
	"raymond.danks@se-eng.com" <raymond.danks@se-eng.com>
Subject: Re: [RFC][PATCH 00/16] Adding python client APIs for glance, quantum and keystone
Date: Thu, 20 Dec 2012 13:20:03 +0100	[thread overview]
Message-ID: <50D30273.8050608@enea.com> (raw)
In-Reply-To: <CADkTA4OPF=TdJ946osZj5NdnBYQV=hkxDx6km3yUBynFOa_h+Q@mail.gmail.com>



On 12/18/2012 03:50 PM, Bruce Ashfield wrote:
>
>
>
> On Tue, Dec 18, 2012 at 9:31 AM, David Nyström <david.c.nystrom@gmail.com
> <mailto:david.c.nystrom@gmail.com>> wrote:
>
>      Sending these patches as an RFC since it includes a removal of a meta-virt
>      patch on
>      python-2.7.3. Also, some of the common python packages might not be optimal
>      to keep in the
>      meta-virtualization layer, some should perhaps be sent as package updates to
>      oe-core.
>
>
> I'd agree that it might not be optimal to have some of the python packages in this
> layer, since they are more about access libraries, communications wrappers and
> security.
>
> The problem with targeting oe-core is that we really need more than just meta-virt
> as a user to make them a reasonable candidate for merging. We'd need Richard
> or Saul to comment on the possibility of merging them to oe-core.
>

> That being said, if it isn't oe-core, the other options seem like the
> meta-networking
> layer, or some of the security layers. The risk with that approach is that we take
> what is a currently simple layer dependency list and make it more complicated.
>
> I can't say that I like adding complexity, but if we can't get them into
> oe-core, then
> it makes sense, to try and get them into a common layer that holds similar
> functionality.
>
> The problem is the timeframe ... if we try and immediately place these in the right
> layer(s), then making them available at all will take some time. So from that point
> of view, we can drop them in meta-virt and start the conversation about where they
> should be in the longer term.
>
> Comments ? I can't say that any of the options really stand out for me :)
>

I suggest we split the recipes which we don't see direct ownership of 
(i.e. a common usecase) into recipes-external/* as a first step.
Step two would be to find a suitable upstream for each package, with the 
end goal to have recipes-external empty.

Somewhat OT:
I really see some improvement the way 
disutils.bbclass/setuptools.bbclass work today,
I've improved create-recipe to understand python source-tarballs, early 
patch on yocto ML, which makes the tedious task of adding python 
dependencies somewhat easier. But alot of the metadata available in the 
python source packages should be able to be automated with bitbake via 
an inherited bbclass.

RDEPENDS, sub package-split et.c. most of the metadata is already 
avaiable in dist/setuptools enables packages. The added bonus of 
automating as much as possible would be a common layout of most 
packages. Is anyone aware of any previous work in this direction ?

> Cheers,
>
> Bruce
>
>      David Nyström (16):
>         Removed meta-virtualization private patch, and using upstream instead
>         Added python-cliff recipe
>         Added python-cmd2 recipe
>         Added python-httplib2 recipe
>         Added python-jsonpatch recipe
>         Added python-jsonpointer recipe
>         Added python-jsonschema recipe
>         Added python-prettytable recipe
>         Added python-pycrypto recipe
>         Added python-pyopenssl recipe
>         Added python-pyparsing recipe
>         Added python-simplejson recipe
>         Added python-warlock recipe
>         Added python-glanceclient recipe
>         Added python-quantumclient recipe
>         Added python-keystoneclient recipe
>
>        .../glanceclient/python-glanceclient_git.bb
>      <http://python-glanceclient_git.bb>        |   26 ++++
>        .../keystoneclient/python-keystoneclient_git.bb
>      <http://python-keystoneclient_git.bb>    |   24 ++++
>        .../quantumclient/python-quantumclient_git.bb
>      <http://python-quantumclient_git.bb>      |   23 ++++
>        .../01-use-proper-tools-for-cross-build.patch      |  138 --------------------
>        recipes-devtools/python/python_2.7.3.bbappend      |    9 --
>        .../files/001-remove-distribute-dependency.patch   |   24 ++++
>        recipes-python/cliff/python-cliff_1.3.bb <http://python-cliff_1.3.bb>
>             |   29 ++++
>        recipes-python/cmd2/python-cmd2_0.6.4.bb <http://python-cmd2_0.6.4.bb>
>             |   20 +++
>        recipes-python/httplib2/python-httplib2_0.7.7.bb
>      <http://python-httplib2_0.7.7.bb>   |   19 +++
>        recipes-python/jsonpatch/python-jsonpatch_0.10.bb
>      <http://python-jsonpatch_0.10.bb>  |   20 +++
>        .../jsonpointer/python-jsonpointer_0.5.bb
>      <http://python-jsonpointer_0.5.bb>          |   16 +++
>        recipes-python/jsonschema/python-jsonschema_0.7.bb
>      <http://python-jsonschema_0.7.bb> |   22 ++++
>        .../prettytable/python-prettytable_0.6.1.bb
>      <http://python-prettytable_0.6.1.bb>        |   18 +++
>        recipes-python/pyOpenSSL/python-pyopenssl_0.13.bb
>      <http://python-pyopenssl_0.13.bb>  |   20 +++
>        .../pycrypto/files/001-remove-includes.patch       |   11 ++
>        recipes-python/pycrypto/python-pycrypto_2.6.bb
>      <http://python-pycrypto_2.6.bb>     |   46 +++++++
>        recipes-python/pyparsing/python-pyparsing_1.5.6.bb
>      <http://python-pyparsing_1.5.6.bb> |   22 ++++
>        .../simplejson/python-simplejson_2.6.2.bb
>      <http://python-simplejson_2.6.2.bb>          |   21 +++
>        recipes-python/warlock/python-warlock_0.7.0.bb
>      <http://python-warlock_0.7.0.bb>     |   26 ++++
>        19 files changed, 387 insertions(+), 147 deletions(-)
>        create mode 100644 recipes-cloud/glanceclient/python-glanceclient_git.bb
>      <http://python-glanceclient_git.bb>
>        create mode 100644
>      recipes-cloud/keystoneclient/python-keystoneclient_git.bb
>      <http://python-keystoneclient_git.bb>
>        create mode 100644 recipes-cloud/quantumclient/python-quantumclient_git.bb
>      <http://python-quantumclient_git.bb>
>        delete mode 100644
>      recipes-devtools/python/python/01-use-proper-tools-for-cross-build.patch
>        delete mode 100644 recipes-devtools/python/python_2.7.3.bbappend
>        create mode 100644
>      recipes-python/cliff/files/001-remove-distribute-dependency.patch
>        create mode 100644 recipes-python/cliff/python-cliff_1.3.bb
>      <http://python-cliff_1.3.bb>
>        create mode 100644 recipes-python/cmd2/python-cmd2_0.6.4.bb
>      <http://python-cmd2_0.6.4.bb>
>        create mode 100644 recipes-python/httplib2/python-httplib2_0.7.7.bb
>      <http://python-httplib2_0.7.7.bb>
>        create mode 100644 recipes-python/jsonpatch/python-jsonpatch_0.10.bb
>      <http://python-jsonpatch_0.10.bb>
>        create mode 100644 recipes-python/jsonpointer/python-jsonpointer_0.5.bb
>      <http://python-jsonpointer_0.5.bb>
>        create mode 100644 recipes-python/jsonschema/python-jsonschema_0.7.bb
>      <http://python-jsonschema_0.7.bb>
>        create mode 100644 recipes-python/prettytable/python-prettytable_0.6.1.bb
>      <http://python-prettytable_0.6.1.bb>
>        create mode 100644 recipes-python/pyOpenSSL/python-pyopenssl_0.13.bb
>      <http://python-pyopenssl_0.13.bb>
>        create mode 100644 recipes-python/pycrypto/files/001-remove-includes.patch
>        create mode 100644 recipes-python/pycrypto/python-pycrypto_2.6.bb
>      <http://python-pycrypto_2.6.bb>
>        create mode 100644 recipes-python/pyparsing/python-pyparsing_1.5.6.bb
>      <http://python-pyparsing_1.5.6.bb>
>        create mode 100644 recipes-python/simplejson/python-simplejson_2.6.2.bb
>      <http://python-simplejson_2.6.2.bb>
>        create mode 100644 recipes-python/warlock/python-warlock_0.7.0.bb
>      <http://python-warlock_0.7.0.bb>
>
>      --
>      1.7.9.5
>
>
>
>
> --
> "Thou shalt not follow the NULL pointer, for chaos and madness await thee at its
> end"
>


  reply	other threads:[~2012-12-20 12:20 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-18 14:31 [RFC][PATCH 00/16] Adding python client APIs for glance, quantum and keystone David Nyström
2012-12-18 14:31 ` [RFC][PATCH 01/16] Removed meta-virtualization private patch, and using upstream instead David Nyström
2012-12-18 14:43   ` Bruce Ashfield
2012-12-20 11:53     ` David Nyström
2012-12-18 14:31 ` [RFC][PATCH 02/16] Added python-cliff recipe David Nyström
2012-12-18 14:31 ` [RFC][PATCH 03/16] Added python-cmd2 recipe David Nyström
2012-12-18 14:31 ` [RFC][PATCH 04/16] Added python-httplib2 recipe David Nyström
2012-12-18 14:31 ` [RFC][PATCH 05/16] Added python-jsonpatch recipe David Nyström
2012-12-18 14:31 ` [RFC][PATCH 06/16] Added python-jsonpointer recipe David Nyström
2012-12-18 14:31 ` [RFC][PATCH 07/16] Added python-jsonschema recipe David Nyström
2012-12-18 14:31 ` [RFC][PATCH 08/16] Added python-prettytable recipe David Nyström
2012-12-18 14:31 ` [RFC][PATCH 09/16] Added python-pycrypto recipe David Nyström
2012-12-18 14:31 ` [RFC][PATCH 10/16] Added python-pyopenssl recipe David Nyström
2012-12-18 14:31 ` [RFC][PATCH 11/16] Added python-pyparsing recipe David Nyström
2012-12-18 14:31 ` [RFC][PATCH 12/16] Added python-simplejson recipe David Nyström
2012-12-18 14:31 ` [RFC][PATCH 13/16] Added python-warlock recipe David Nyström
2012-12-18 14:31 ` [RFC][PATCH 14/16] Added python-glanceclient recipe David Nyström
2012-12-18 14:31 ` [RFC][PATCH 15/16] Added python-quantumclient recipe David Nyström
2012-12-18 14:40   ` Bruce Ashfield
2012-12-20 11:56     ` David Nyström
2012-12-18 14:31 ` [RFC][PATCH 16/16] Added python-keystoneclient recipe David Nyström
2012-12-18 14:50 ` [RFC][PATCH 00/16] Adding python client APIs for glance, quantum and keystone Bruce Ashfield
2012-12-20 12:20   ` David Nyström [this message]
2012-12-20 16:39     ` Bruce Ashfield

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=50D30273.8050608@enea.com \
    --to=david.nystrom@enea.com \
    --cc=bruce.ashfield@gmail.com \
    --cc=meta-virtualization@yoctoproject.org \
    --cc=raymond.danks@se-eng.com \
    /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.