From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Randy MacLeod <randy.macleod@windriver.com>,
Chen Qi <Qi.Chen@windriver.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/3] systemd: upgrade to 237
Date: Fri, 16 Mar 2018 21:27:51 +0200 [thread overview]
Message-ID: <88e2bc77-5959-fe48-6372-da4f0c017e15@linux.intel.com> (raw)
In-Reply-To: <a0a682c8-6b75-2fa7-eba8-b451d09b1230@windriver.com>
On 03/16/2018 09:30 PM, Randy MacLeod wrote:
>> This new version has dropped ptest support, as there's no easy
>> way to do this in the framework of meson.
>
> Are you talking to the meson developers to see if we/they can
> come up with a way to do that? Is there an issue opened:
> https://github.com/mesonbuild/meson/issues
> I didn't find one.
Yes - please be more specific. What are the difficulties in building and
packaging tests when meson is used, as compared to autotools? If you
need to patch meson build files in systemd source tree, it's totally
fine to do that.
Alex
next prev parent reply other threads:[~2018-03-16 19:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 8:38 [PATCH 0/3] systemd & systemd-boot: upgrade to 237 Chen Qi
2018-03-12 8:38 ` [PATCH 1/3] systemd: " Chen Qi
2018-03-12 8:52 ` Maxin B. John
2018-03-12 9:16 ` ChenQi
2018-03-16 19:30 ` Randy MacLeod
2018-03-16 19:27 ` Alexander Kanavin [this message]
2018-03-19 4:53 ` ChenQi
2018-03-19 5:21 ` Khem Raj
2018-03-19 9:04 ` Alexander Kanavin
2018-03-22 6:06 ` ChenQi
2018-03-22 11:14 ` Alexander Kanavin
2018-03-22 16:12 ` Randy MacLeod
2018-03-22 16:14 ` Burton, Ross
2018-03-22 16:30 ` Khem Raj
2018-03-20 17:19 ` Alex Kiernan
2018-03-20 17:36 ` Khem Raj
2018-03-20 18:00 ` Burton, Ross
2018-03-22 7:36 ` ChenQi
2018-03-12 8:38 ` [PATCH 2/3] systemd: fix build failure for qemux86 and qemuppc with musl Chen Qi
2018-03-12 8:38 ` [PATCH 3/3] systemd-boot: upgrade to 237 Chen Qi
2018-03-12 8:43 ` [PATCH 0/3] systemd & " ChenQi
2018-03-15 1:59 ` ChenQi
2018-03-15 10:51 ` Burton, Ross
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=88e2bc77-5959-fe48-6372-da4f0c017e15@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=Qi.Chen@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=randy.macleod@windriver.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