From: Jack <ostroffjh@users.sourceforge.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Why busybox?
Date: Sun, 05 Apr 2020 16:57:26 -0400 [thread overview]
Message-ID: <EV7IAL4D.YST6XSKB.LRMZ4DJ5@OLBAPZNP.YSPZQ23L.UQ3Z2DSQ> (raw)
In-Reply-To: <CAK2H+edf5apFB7KXS-7hVCBDhAuVinxg-qHhEkUA6_ghQHkMPw@mail.gmail.com> (from markknecht@gmail.com on Sun Apr 5 16:03:51 2020)
On 2020.04.05 16:03, Mark Knecht wrote:
> On Sun, Apr 5, 2020 at 10:54 AM Ian Zimmerman <itz@very.loosely.org>
> wrote:
> >
> > Why does portage insist on installing busybox for me?
> >
> > As far as I know the only use for it on a desktop system is for
> > initramfs. I have no initramfs, therefore I have no need for
> busybox.
> > I unmerged it and nothing bad happened except for a warning from
> portage
> > that it is part of my profile set. I went ahead and ignored the
> > warning.
> >
> > But now I updated the tree and emerge -p shows it will be installed
> > again. Why is that? The only reverse dependencies are virtuals
> which
> > are satisfied in other ways, like virtual/awk. So is it the profile
> > thing? But I have done the same with other profile packages
> (notably
> > editors/nano) and those are _not_ coming back.
> >
> > --
> > Ian
>
> emerge is your friend. Something like
>
> emerge -p -e
>
> should. I believe, tell you where every package dependency comes from.
>
> It's not always fun to read but the answer to your question should be
> there.
>
> - Mark
I find "emerge -p -c busybox" even easier, and it tells me busybox is
required by @system.
Jack
prev parent reply other threads:[~2020-04-05 20:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-05 17:53 [gentoo-user] Why busybox? Ian Zimmerman
2020-04-05 18:45 ` Ashley Dixon
2020-04-05 19:56 ` [gentoo-user] " Ian Zimmerman
2020-04-05 20:19 ` Ashley Dixon
2020-04-05 21:09 ` Neil Bothwick
2020-04-06 8:52 ` Adam Carter
2020-04-05 20:03 ` [gentoo-user] " Mark Knecht
2020-04-05 20:18 ` Dale
2020-04-05 20:20 ` Mark Knecht
2020-04-05 20:57 ` Jack [this message]
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=EV7IAL4D.YST6XSKB.LRMZ4DJ5@OLBAPZNP.YSPZQ23L.UQ3Z2DSQ \
--to=ostroffjh@users.sourceforge.net \
--cc=gentoo-user@lists.gentoo.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