From: "Gábor Boskovits" <boskovits@gmail.com>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: symphonia@disroot.org, 39023@debbugs.gnu.org
Subject: bug#39023: binary installation manual doesn't work on Alpine Linux
Date: Wed, 22 Jan 2020 21:03:04 +0100 [thread overview]
Message-ID: <CAE4v=pgMQ9-Gd6WpvsAY3OWQ_Cd7PCUouS4Vwfv4cp4mDBD1bw@mail.gmail.com> (raw)
In-Reply-To: <87lfpzfel9.fsf@nckx>
Tobias Geerinckx-Rice <me@tobias.gr> ezt írta (időpont: 2020. jan.
22., Sze, 20:58):
>
> Gábor,
>
> Gábor Boskovits 写道:
> > Oops, I missed that.
>
> I'm suprised I haven't confused add* & *add once so far in this
> thread :-)
Yes, I am also a bit confused.
>
> > There was some upstream discussion to get useradd and groupadd
> > to
> > busybox upstream,
> > as this seems to be causing problems everywhere. They told that
> > they
> > are unwilling to include them as is,
> > but would accept a wrapper thar forward to their
> > adduser/addgroup
> > implementation.
>
> I don't know which discussion you're referring to, and much might
> have changed since 2016, but I read this[0] to mean the opposite:
> Busybox should provide the shadow-compatible *add variants, and
> reimplement their old add* as simple wrappers around that. That's
> from an upstream(ish) person.
>
> “adduser/addgroup tend to be symlinks or wrappers, if they exist
> at
> all, but by and large are deprecated. busybox should implement
> applets that mimic shadow here and deprecate the old ones, if
> not
> throw them out. although we can probably rename & massage the
> sources in these cases”
>
> Still, Busybox *add patches welcome, it would seem. We'll still
> have to deal with this for the lifetime of the older version.
Yes, I referred to this, but I might have misunderstood something.
>
> Kind regards,
>
> T G-R
>
> [0]:
> http://lists.busybox.net/pipermail/busybox/2016-February/083909.html
--
OpenPGP Key Fingerprint: 7988:3B9F:7D6A:4DBF:3719:0367:2506:A96C:CF63:0B21
next prev parent reply other threads:[~2020-01-22 20:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-07 21:29 bug#39023: binary installation manual doesn't work on Alpine Linux symphonia
2020-01-08 12:34 ` Gábor Boskovits
2020-01-22 3:53 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-01-22 19:42 ` Gábor Boskovits
2020-01-22 19:58 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-01-22 20:03 ` Gábor Boskovits [this message]
2020-02-19 15:56 ` zimoun
2020-01-22 1:44 ` bug#39023: adduser/addgroup vs useradd/groupadd zimoun
2020-01-22 4:03 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-01-22 8:31 ` zimoun
2020-04-23 11:55 ` bug#39023: binary installation manual doesn't work on Alpine Linux Vincent Legoll
2020-04-23 13:29 ` zimoun
2020-04-23 14:15 ` Vincent Legoll
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAE4v=pgMQ9-Gd6WpvsAY3OWQ_Cd7PCUouS4Vwfv4cp4mDBD1bw@mail.gmail.com' \
--to=boskovits@gmail.com \
--cc=39023@debbugs.gnu.org \
--cc=me@tobias.gr \
--cc=symphonia@disroot.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).