From: "Khem Raj" <raj.khem@gmail.com>
To: Dan Callaghan <dan.callaghan@opengear.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] stress-ng: create a symlink for /usr/bin/stress
Date: Thu, 23 Jul 2020 01:31:49 -0700 [thread overview]
Message-ID: <CAMKF1srjxVscx=cWo-geuvs0-NORhL1zEx5jKpbUppobpSobiQ@mail.gmail.com> (raw)
In-Reply-To: <1595491143-sup-2728@galangal.danc.bne.opengear.com>
On Thu, Jul 23, 2020 at 1:06 AM Dan Callaghan
<dan.callaghan@opengear.com> wrote:
>
> Excerpts from Khem Raj's message of 2020-07-22 23:09:23 -07:00:
> > there is stress recipe in some layers which could provide stress
> > utility as well, therefore it should be using update-alternatives
> > mechanism so it fills in when stress is not provided by say stress
> > recipe.
>
> Hmm... The stress-ng recipe already RPROVIDES stress though. Doesn't
> that make it incompatible with any other existing stress recipe and
> update-alternatives?
>
> Personally I think alternatives is overkill here, and stress-ng should
> not RPROVIDES stress at all (that is, revert commit 72641004). In that
> case, we would have noticed that the stress recipe had been removed from
> oe-core and we could have just updated our image accordingly to depend
> on stress-ng instead.
>
yeah I think its a fair point, we already are providing it in that
case we can live with unconditional
symlink and let older stress recipe deal with conflicts if someone needs it
> > secondly please use ${D}${bindir}/stress instead of hardcoding the path
>
> Oops, yes of course.
>
> --
> Dan Callaghan <dan.callaghan@digi.com>
> Software Engineer
> Opengear <https://opengear.com/>
>
next prev parent reply other threads:[~2020-07-23 8:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 4:31 [PATCH] stress-ng: create a symlink for /usr/bin/stress Dan Callaghan
2020-07-23 6:09 ` [OE-core] " Khem Raj
2020-07-23 8:06 ` Dan Callaghan
2020-07-23 8:31 ` Khem Raj [this message]
2020-07-23 8:50 ` [PATCH v2] " Dan Callaghan
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='CAMKF1srjxVscx=cWo-geuvs0-NORhL1zEx5jKpbUppobpSobiQ@mail.gmail.com' \
--to=raj.khem@gmail.com \
--cc=dan.callaghan@opengear.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.