Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Derek Straka <derek@asterius.io>
Cc: "S. Lockwood-Childs" <sjl@vctlabs.com>,
	openembeded-devel <openembedded-devel@lists.openembedded.org>,
	openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: splitting python's standard library
Date: Tue, 19 Dec 2017 15:12:13 +0200	[thread overview]
Message-ID: <32cbea3c-5275-cd8e-e7ef-7654e1e94bfa@linux.intel.com> (raw)
In-Reply-To: <CADNbA1oCH=x1SoZn-pb50bZabf+rurd1w_o7D9P9FM4u=FXXsQ@mail.gmail.com>

On 12/19/2017 02:31 PM, Derek Straka wrote:
> Well, I've been able to do it just fine for the majority of packages in 
> meta-python by myself.  Since I contribute the majority of the patches 
> and maintain the layer, I want this capability maintained in 
> meta-python.  If you plan on removing that functionality in oe-core, I'd 
> like to have the opportunity to maintain the python recipes there as 
> well rather than have a feature unilaterally removed.  I don't consider 
> it a burden and my customers find it valuable to split things out.

If you're able to take over the maintenance of oe-core's python 
packages, then that's great and much appreciated! I'll send a patch that 
assigns them to you in a moment.

Alex


  reply	other threads:[~2017-12-19 13:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1512414044-1012-1-git-send-email-mark.asselstine@windriver.com>
     [not found] ` <CADNbA1qnmF3-MKo=fqQQeWEedE5A-wzkUkCgdCNArOePjMaXQw@mail.gmail.com>
     [not found]   ` <CAPuovEKdqQP35XwP3bgBrE4EFbM2LwpHrHzxF3my9qaWfAaCbA@mail.gmail.com>
     [not found]     ` <CABcZANku-aE5a69GpJxXmd2F0+uYVhiRZB3Uut7F2RG1e3R9EA@mail.gmail.com>
     [not found]       ` <CAPuovEJNf=qefXX6wKJGaH+HkM6aan49AgVQ3TEWVWPSCn3cNw@mail.gmail.com>
2017-12-18 16:37         ` [oe] [meta-python][PATCH] python-pyroute2: uprev to v0.4.21 (from 0.3.22) Alexander Kanavin
2017-12-18 16:56           ` Mark Asselstine
2017-12-18 20:17             ` Derek Straka
2017-12-18 20:53               ` Mark Asselstine
     [not found]               ` <20171218210256.GQ27580@vctlabs.com>
2017-12-18 21:07                 ` Derek Straka
2017-12-18 21:26                   ` Mark Asselstine
2017-12-18 21:27                     ` Derek Straka
2017-12-19  7:56                 ` splitting python's standard library Alexander Kanavin
2017-12-19 12:31                   ` Derek Straka
2017-12-19 13:12                     ` Alexander Kanavin [this message]
2017-12-19 13:23                       ` Derek Straka
2017-12-19 13:43                         ` [oe] " Burton, Ross
2017-12-19 14:02                           ` Derek Straka
2017-12-28 22:29                             ` Derek Straka

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=32cbea3c-5275-cd8e-e7ef-7654e1e94bfa@linux.intel.com \
    --to=alexander.kanavin@linux.intel.com \
    --cc=derek@asterius.io \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=sjl@vctlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox