Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Denys Dmytriyenko" <denis@denix.org>
To: pb@pbcl.net
Cc: Gregor Zatko <gzatko@gmail.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] update-alternatives: introduce new package as a opkg-utils spin-off
Date: Tue, 2 Jun 2020 15:54:50 -0400	[thread overview]
Message-ID: <20200602195450.GV17660@denix.org> (raw)
In-Reply-To: <20200602194940.GA2207@pbcl.net>

On Tue, Jun 02, 2020 at 09:49:40PM +0200, Phil Blundell via lists.openembedded.org wrote:
> On Tue, Jun 02, 2020 at 09:43:45PM +0200, Gregor Zatko wrote:
> > - if you take a look at 
> > http://git.yoctoproject.org/cgit/cgit.cgi/opkg-utils/tree/update-alternatives
> > you'll simply see it's a shellscript; if we wanted to have it without
> > bash we'd need a C++
> > implementation, am I right?
> 
> No, I think the point is that the shell script only needs /bin/sh.  If it
> required bash specifically then it would have #!/bin/bash at the top.

The original opkg-utils recipe has this:
RDEPENDS_${PN} += "bash"

Note that update-alternatives goes into own package and doesn't have such 
RDEPS.


> But, isn't rpmdeps supposed to sort that out automatically in any case?
> 
> p.
> 

> 


  reply	other threads:[~2020-06-02 19:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-02 19:09 [PATCH] update-alternatives: introduce new package as a opkg-utils spin-off Gregor Zatko
2020-06-02 19:27 ` [OE-core] " Denys Dmytriyenko
2020-06-02 19:43   ` Gregor Zatko
2020-06-02 19:49     ` Phil Blundell
2020-06-02 19:54       ` Denys Dmytriyenko [this message]
2020-06-02 19:32 ` Phil Blundell
2020-06-02 19:43 ` Andreas Oberritter
2020-06-02 19:45   ` Gregor Zatko
2020-06-02 20:06     ` Denys Dmytriyenko

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=20200602195450.GV17660@denix.org \
    --to=denis@denix.org \
    --cc=gzatko@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=pb@pbcl.net \
    /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