From: "Gregor Zatko" <gzatko@gmail.com>
To: Denys Dmytriyenko <denis@denix.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] update-alternatives: introduce new package as a opkg-utils spin-off
Date: Tue, 02 Jun 2020 21:43:45 +0200 [thread overview]
Message-ID: <70201ad445cf106e80c44c3c5fb831501a2efda8.camel@gmail.com> (raw)
In-Reply-To: <20200602192721.GU17660@denix.org>
[-- Attachment #1: Type: text/plain, Size: 1120 bytes --]
On Tue, 2020-06-02 at 15:27 -0400, Denys Dmytriyenko wrote:
> On Tue, Jun 02, 2020 at 09:09:25PM +0200, Gregor Zatko wrote:
> > In some cases there is a need for update-alternatives script which gets built
> > within opkg-utils recipe into a standalone package. However, this causes to
> > many unnecessary dependencies, including Python, bc, OpenSSL etc. to be built.
> >
> > In this commit a standalone lightweight recipe for update-alternatives that
> > shouldn't be dependent on nothing other than bash.
>
> (R)Depending on bash doesn't make it lightweight anymore. This means you
> cannot do tiny bash-less images with alternatives?
Well, if I understand everyting correct then yes, it's not possible.
However, I've
mostly been a user of Yocto so please check my reasoning:
- first, I made a comment here
https://bugzilla.yoctoproject.org/show_bug.cgi?id=8879#c4
- 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?
[-- Attachment #2: Type: text/html, Size: 1775 bytes --]
next prev parent reply other threads:[~2020-06-02 19:43 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 [this message]
2020-06-02 19:49 ` Phil Blundell
2020-06-02 19:54 ` Denys Dmytriyenko
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=70201ad445cf106e80c44c3c5fb831501a2efda8.camel@gmail.com \
--to=gzatko@gmail.com \
--cc=denis@denix.org \
--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.