Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Adrian Bunk" <bunk@stusta.de>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Rasmus Villemoes <rasmus.villemoes@prevas.dk>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH][dunfell] coreutils: don't split stdbuf to own package with single-binary
Date: Sun, 5 Jul 2020 00:10:43 +0300	[thread overview]
Message-ID: <20200704211043.GA24166@localhost> (raw)
In-Reply-To: <5c9d33386f921a0b7fe06bfc480b6d52bfa26708.camel@linuxfoundation.org>

On Fri, Jul 03, 2020 at 11:48:36AM +0100, Richard Purdie wrote:
>...
> I hadn't realised there was already the reverse dependency. I think we
> need to let the package exist in both cases so the two dependencies
> need to reverse direction depending on whether single-binary is set.
>...

What about no separate coreutils-stdbuf package with single-binary,
instead an RPROVIDES of coreutils-stdbuf?

> Cheers,
> 
> Richard

cu
Adrian

  parent reply	other threads:[~2020-07-04 21:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-03  7:36 [PATCH][dunfell] coreutils: don't split stdbuf to own package with single-binary Rasmus Villemoes
2020-07-03  8:17 ` [OE-core] " Alexander Kanavin
2020-07-03  9:19 ` Richard Purdie
2020-07-03  9:29   ` Rasmus Villemoes
2020-07-03 10:48     ` Richard Purdie
2020-07-03 11:51       ` Rasmus Villemoes
2020-07-04 21:10       ` Adrian Bunk [this message]
2020-07-06  7:49         ` Rasmus Villemoes
  -- strict thread matches above, loose matches on Subject: below --
2020-07-09  7:06 [PATCH] [dunfell] " Rasmus Villemoes

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=20200704211043.GA24166@localhost \
    --to=bunk@stusta.de \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=rasmus.villemoes@prevas.dk \
    --cc=richard.purdie@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox