From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Andrew Geissler <geissonator@gmail.com>,
openembedded-core@lists.openembedded.org
Subject: Re: python test files installed in image on purpose?
Date: Tue, 11 Sep 2018 12:01:04 +0100 [thread overview]
Message-ID: <ab989d52f45bf82b397fac9a7efe58ebb19becfe.camel@linuxfoundation.org> (raw)
In-Reply-To: <CALLMt=r-i5AhyYaXon9na0NSky3cvph9ZpbGx0ogeuzOh8pB=w@mail.gmail.com>
On Fri, 2018-09-07 at 14:02 -0500, Andrew Geissler wrote:
> Hi,
>
> We've been running into some flash space issues over in the openbmc
> project. I noticed the python.bb file (python_2.7.14.bb for us) is
> installing some test folders/files in our rootfs image.
>
> # find /usr/lib/python2.7/ -name "test" -print
> /usr/lib/python2.7/ctypes/test
> /usr/lib/python2.7/email/test
>
> I'm looking to see if there's any functional reason these tests are
> included in the image.
>
> In our compressed filesystem we're talking about ~150KB of space but
> right now that's a pretty big deal for us. Would the community be
> interested in a patch to not install (or make it an option like is
> done with INCLUDE_PYCS) these test files? Or is this something we
> should just handle in a .bbappend file for our distro?
>
> Here's a complete list of test directories in the python package.
> ./Python-2.7.14/Lib/bsddb/test
> ./Python-2.7.14/Lib/sqlite3/test
> ./Python-2.7.14/Lib/ctypes/test
> ./Python-2.7.14/Lib/unittest/test
> ./Python-2.7.14/Lib/lib-tk/test
> ./Python-2.7.14/Lib/email/test
These definitely sound like they should be put into a different package
which is related to testing and not installed otherwise.
So yes, in principle these are exactly the kinds of fixes which should
be going into core!
Cheers,
Richard
prev parent reply other threads:[~2018-09-11 11:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-07 19:02 python test files installed in image on purpose? Andrew Geissler
2018-09-10 19:56 ` Alejandro Enedino Hernandez Samaniego
2018-09-11 11:01 ` Richard Purdie [this message]
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=ab989d52f45bf82b397fac9a7efe58ebb19becfe.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=geissonator@gmail.com \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox