That's a very good question.
I myself haven't seen python unit tests used via ptests in the wild, but
if that is used, yes fully agree, it should be rather PN-ptests than
PN-tests.
BTW it would also require to create a run-ptest file, which would
complicate things even more.
Regards
Konrad
On 07.07.20 21:25, Richard Purdie wrote:
On Tue, 2020-07-07 at 21:01 +0200, Konrad Weihmann wrote:
Put files from installed tests into a separate package to avoid
having
them in an image unwanted and to avoid having more runtime
dependencies than necessary.
Background:
As setuptools is pretty much unregulated in terms what is installed
by some module, even tests are installed into base package, which
then
go right into production, although completely unnecessary.
When now trying to determine the needed runtime dependencies, more
than actually needed will slip into the image.
To give a really bad example GitPython ships its tests into
production
leading to the effect that theoretically besides the known RDEPENDS
python3-asyncio, python3-distutils, python3-idle, python3-misc,
python3-pickle, python3-shell, python3-ddt and python3-nose would be
required.
That's why I came up with the idea to package tests (if existing)
into
a separate package, which is NOT installed by default.
Please let me know if you see any issues with that patch
Shouldn't these be part of a PN-ptests package to match the rest of the
system?
Cheers,
Richard
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#140385):
https://lists.openembedded.org/g/openembedded-core/message/140385
Mute This Topic: https://lists.openembedded.org/mt/75361807/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
