All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Volk <f_l_k@t-online.de>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [oe-core][PATCH] glib-2.0: update 2.82.4 -> 2.84.0
Date: Fri, 07 Mar 2025 15:33:24 +0100	[thread overview]
Message-ID: <OFCRSS.DMAMQS5P3JTF@t-online.de> (raw)
In-Reply-To: <182A8AC2C61D2C82.9571@lists.openembedded.org>

[-- Attachment #1: Type: text/plain, Size: 742 bytes --]

taptestrunner.py testprogramrunner.py

These two files are installed in ${libexecdir}/installed-tests

And looking at its meson.build this seems to be the default location

<https://gitlab.gnome.org/GNOME/glib/-/blob/main/tests/lib/meson.build?ref_type=heads>

Should they go to ${datadir}/installed-tests ?

On Fri, Mar 7 2025 at 15:13:32 +01:00:00, Markus Volk 
<f_l_k@t-online.de> wrote:
> On Fri, Mar 7 2025 at 15:05:26 +01:00:00, Alexander Kanavin 
> <alex.kanavin@gmail.com> wrote:
>> This needs to be explained, as it doesn't seem correct, and
>> contradicts ptest-gnome which (correctly) installs these to the ptest
>> package.
> 
> I see. I think the issue here is, that the install path changed from 
> ${datadir} to ${libexecdir}


[-- Attachment #2: Type: text/html, Size: 1220 bytes --]

  parent reply	other threads:[~2025-03-07 14:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-07 13:29 [oe-core][PATCH] glib-2.0: update 2.82.4 -> 2.84.0 Markus Volk
2025-03-07 14:05 ` Alexander Kanavin
2025-03-07 14:13   ` Markus Volk
     [not found]   ` <182A8AC2C61D2C82.9571@lists.openembedded.org>
2025-03-07 14:33     ` Markus Volk [this message]
2025-03-07 14:47       ` Alexander Kanavin
2025-03-07 15:09         ` Markus Volk
     [not found]         ` <182A8DD37F985901.9571@lists.openembedded.org>
2025-03-07 15:32           ` Markus Volk
     [not found]           ` <182A8F15FD14C8CF.13616@lists.openembedded.org>
2025-03-07 16:20             ` Markus Volk
2025-03-07 15:21 ` Richard Purdie

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=OFCRSS.DMAMQS5P3JTF@t-online.de \
    --to=f_l_k@t-online.de \
    --cc=alex.kanavin@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 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.