From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Marcus Hoffmann <buildroot@bubu1.eu>
Cc: buildroot@buildroot.org, Marcus Hoffmann <bubu@bubu1.eu>
Subject: Re: [Buildroot] [PATCH 2/2] support/testing: python-varlink: new runtime test
Date: Sat, 27 Dec 2025 21:57:44 +0100 [thread overview]
Message-ID: <20251227215744.79d17b9b@windsurf> (raw)
In-Reply-To: <20251124140517.2833351-2-buildroot@bubu1.eu>
On Mon, 24 Nov 2025 15:05:16 +0100
Marcus Hoffmann <buildroot@bubu1.eu> wrote:
> Add new runtime test for python-varlink. Add this in a subdirectory, so
> the separate example interface file (which should be named in reverse
> DNS notation) does not sit loosly in the general package test dir.
I changed this to not have the test in a subdir. I kept the interface
file and sample script in a subdir, but not the test itself.
The reason: consistency with other tests, that have the same
organization, the test is in support/testing/tests/packages/, and there
is a subdir for the artifacts that are needed for the test to run.
Applied with this small change. Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-12-27 20:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-24 14:05 [Buildroot] [PATCH 1/2] package/python-varlink: new package Marcus Hoffmann via buildroot
2025-11-24 14:05 ` [Buildroot] [PATCH 2/2] support/testing: python-varlink: new runtime test Marcus Hoffmann
2025-12-27 20:57 ` Thomas Petazzoni via buildroot [this message]
2025-12-27 20:56 ` [Buildroot] [PATCH 1/2] package/python-varlink: new package Thomas Petazzoni via buildroot
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=20251227215744.79d17b9b@windsurf \
--to=buildroot@buildroot.org \
--cc=bubu@bubu1.eu \
--cc=buildroot@bubu1.eu \
--cc=thomas.petazzoni@bootlin.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.