All of lore.kernel.org
 help / color / mirror / Atom feed
From: "S. Lockwood-Childs" <sjl@vctlabs.com>
To: Derek Straka <derek@asterius.io>
Cc: Mark Asselstine <mark.asselstine@windriver.com>,
	openembeded-devel <openembedded-devel@lists.openembedded.org>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [meta-python][PATCH] python-pyroute2: uprev to v0.4.21 (from 0.3.22)
Date: Mon, 18 Dec 2017 13:02:56 -0800	[thread overview]
Message-ID: <20171218210256.GQ27580@vctlabs.com> (raw)
In-Reply-To: <CADNbA1psOtOeCcsLaSM4VWJV5PXqe=HmE9BuxcR4UYkJp5Erdw@mail.gmail.com>

On Mon, Dec 18, 2017 at 03:17:25PM -0500, Derek Straka wrote:
> I have several customers who have optimized for space and would like to see
> the capability maintained unless core removes the ability to split python
> packages out.  They also remove the *.py files in favor of *.pyo files (via
> a custom packaging mechanism).  I have automated tests that go through the
> module importing on each of the meta-python packages to ensure it works on
> minimal python installations.  When other contributors don't do provide
> that functionality, I either catch it when I do package update or when it
> breaks for one of my customers.  I'm fine if you don't want to perform the
> checks yourself and it breaks my use case with missing dependencies, but I
> would prefer that you don't remove the dependencies that are currently in
> place.  Thanks.

Me too -- some of my projects still use NAND for rootfs, where space is tight and
ability to split out python modules is very useful. Thus it is not an unused
feature, though many projects have SD/eMMC for rootfs and those ones generally
will not care about it.


  parent reply	other threads:[~2017-12-18 21:00 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-04 19:00 [meta-python][PATCH] python-pyroute2: uprev to v0.4.21 (from 0.3.22) Mark Asselstine
2017-12-16 21:58 ` Derek Straka
2017-12-18 15:33   ` Mark Asselstine
2017-12-18 15:36     ` Christopher Larson
2017-12-18 16:15       ` Mark Asselstine
2017-12-18 16:37         ` Alexander Kanavin
2017-12-18 16:37           ` [oe] " Alexander Kanavin
2017-12-18 16:56           ` Mark Asselstine
2017-12-18 16:56             ` [oe] " Mark Asselstine
2017-12-18 20:17             ` Derek Straka
2017-12-18 20:17               ` [oe] " Derek Straka
2017-12-18 20:53               ` Mark Asselstine
2017-12-18 20:53                 ` [oe] " Mark Asselstine
2017-12-18 21:02               ` S. Lockwood-Childs [this message]
2017-12-18 21:07                 ` Derek Straka
2017-12-18 21:07                   ` [oe] " Derek Straka
2017-12-18 21:26                   ` Mark Asselstine
2017-12-18 21:26                     ` [oe] " Mark Asselstine
2017-12-18 21:27                     ` Derek Straka
2017-12-18 21:27                       ` [oe] " Derek Straka
2017-12-19  7:56                 ` splitting python's standard library Alexander Kanavin
2017-12-19 12:31                   ` Derek Straka
2017-12-19 12:31                     ` Derek Straka
2017-12-19 13:12                     ` Alexander Kanavin
2017-12-19 13:12                       ` Alexander Kanavin
2017-12-19 13:23                       ` Derek Straka
2017-12-19 13:23                         ` Derek Straka
2017-12-19 13:43                         ` Burton, Ross
2017-12-19 13:43                           ` [oe] " Burton, Ross
2017-12-19 14:02                           ` Derek Straka
2017-12-19 14:02                             ` [oe] " Derek Straka
2017-12-28 22:29                             ` Derek Straka
2017-12-28 22:29                               ` [oe] " 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=20171218210256.GQ27580@vctlabs.com \
    --to=sjl@vctlabs.com \
    --cc=derek@asterius.io \
    --cc=mark.asselstine@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=openembedded-devel@lists.openembedded.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.