All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ashish Mishra" <emailaddress.ashish@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [scarthgap][PATCH v2] imagemagick: adds ptest for imagemagick recipe
Date: Thu, 06 Nov 2025 01:39:16 -0800	[thread overview]
Message-ID: <193319.1762421956956925614@lists.openembedded.org> (raw)
In-Reply-To: <CA+s=J=y=OWL_KfpjtZcewF5Qsb1gW4-eLAGp+Tw9CQ6mqTHSHQ@mail.gmail.com>

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

Dear Anuj ,

1) For scarthgap imagemagick version uses "convert" binary for its central operations whereas latest version of imagemagick uses "magick" [ in master ]

master       : *"magick"   is central binary and all other supporting binaries are symlink to it*
scarthgap  : *"convert" is central binary and all other supporting binaries are symlink to it*

2) Have created same ptest (with "magick" ) for master branch @ https://lists.openembedded.org/g/openembedded-devel/topic/meta_oe_master_patch_v2/116149980
This causes same patch logic but with respective central binaries to be used in their respective branches

3) I can rework on logic if any suggestion from team or if there is another suggested approach for such scenario

Thanks ,

Ashish Kumar Mishra

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

  reply	other threads:[~2025-11-06  9:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-28 10:28 [scarthgap][PATCH v2] imagemagick: adds ptest for imagemagick recipe AshishKumar Mishra
2025-10-29 12:30 ` Ashish Mishra
2025-10-29 12:49   ` [oe] " Gyorgy Sarvari
2025-10-30  5:14     ` AshishKumar Mishra
2025-11-03  4:48       ` AshishKumar Mishra
2025-11-04  9:29         ` Ashish Mishra
2025-11-06  5:16           ` AshishKumar Mishra
2025-11-06  5:59             ` [oe] " Anuj Mittal
2025-11-06  9:39               ` Ashish Mishra [this message]
2025-11-10  9:38                 ` AshishKumar Mishra
2025-11-12  2:40                   ` [oe] " Anuj Mittal

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=193319.1762421956956925614@lists.openembedded.org \
    --to=emailaddress.ashish@gmail.com \
    --cc=openembedded-devel@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.