From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] How to resume 'emerge -e @world' after grub fails?
Date: Mon, 18 Dec 2017 17:38:50 -0600 [thread overview]
Message-ID: <f77d4313-8c2f-d59f-c776-7c25f7de235b@gmail.com> (raw)
In-Reply-To: <CAC=wYCG4THZH7tHjnO8v1dZS2+d9Fh4JjS=Ywt1wCcXG8w=R=w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1705 bytes --]
Adam Carter wrote:
>
> I have to confess, I set most of this as defaults in make.conf. The
> most often commands I use, eix-sync and emerge -uaDN world.
> Everything
> else is in make.conf. Listy for those who may be curious.
>
> EMERGE_DEFAULT_OPTS="--with-bdeps y --backtrack=100 --keep-going
> -v -j5
> --quiet-build=n -1 --unordered-display"
>
> FEATURES="-usersync userpriv usersandbox buildpkg sandbox
> parallel-fetch"
>
> Each of those were added as I noticed I needed them more often than
> not. The backtrack option started out at 50 but sometimes that wasn't
> enough so I increased it to 100. That has worked well so far. The
> --oneshot, (-1), option was to keep unneeded things from being
> added to
> my world file. Each option has some reason for being there.
>
>
> Won't the -1 mean that --depclean will remove packages that you want?
>
If I emerge something and want to keep around, I use the --select y
option which overrides the -1 option in make.conf. Sometimes I install
something, play with it and don't like it and then let --depclean remove
it. If I emerge something and like it, I can use --select y -n to add
it to world, without compiling it again.
The key thing, remembering to force it to be added to world, which is a
lot easier than remembering to use -1 for ALL those things I don't want
in the world file. Before I added the -1 option, my world file was full
of all sorts of things that have no business being there at all. It was
causing huge problems with upgrades and such.
I just use what works for me. Some may not like doing it this way but
some might.
Dale
:-) :-)
[-- Attachment #2: Type: text/html, Size: 2921 bytes --]
next prev parent reply other threads:[~2017-12-18 23:39 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 16:00 [gentoo-user] How to resume 'emerge -e @world' after grub fails? Grant Edwards
2017-12-18 16:07 ` John Blinka
2017-12-18 16:14 ` [gentoo-user] " Grant Edwards
2017-12-18 16:45 ` Dale
2017-12-20 20:16 ` Grant Edwards
2017-12-20 23:28 ` Dale
2017-12-21 8:43 ` Mart Raudsepp
2017-12-21 9:45 ` Jörg Schaible
2017-12-21 12:00 ` Marc Joliet
2017-12-21 17:02 ` John Covici
2018-01-07 12:39 ` Marc Joliet
2017-12-21 17:13 ` Jörg Schaible
2018-01-07 12:41 ` Marc Joliet
2017-12-21 17:32 ` Grant Edwards
2017-12-18 16:14 ` [gentoo-user] " Dale
2017-12-18 17:55 ` Mick
2017-12-18 19:02 ` David Haller
2017-12-18 19:31 ` Francisco Ares
2017-12-18 20:05 ` David Haller
2017-12-18 22:49 ` Dale
2017-12-18 23:05 ` Adam Carter
2017-12-18 23:38 ` Dale [this message]
2017-12-19 3:06 ` David Haller
2017-12-19 4:03 ` Dale
2017-12-20 22:54 ` David Haller
2017-12-21 4:49 ` Dale
2017-12-19 5:51 ` Adam Carter
2017-12-19 9:15 ` Neil Bothwick
2017-12-19 15:45 ` Helmut Jarausch
2017-12-19 18:13 ` Bas Zoutendijk
2017-12-20 8:08 ` Helmut Jarausch
2017-12-20 22:27 ` David Haller
2017-12-19 17:45 ` Dale
2017-12-19 20:22 ` Neil Bothwick
2017-12-20 2:04 ` Adam Carter
2017-12-20 23:18 ` David Haller
2017-12-19 9:21 ` Neil Bothwick
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=f77d4313-8c2f-d59f-c776-7c25f7de235b@gmail.com \
--to=rdalek1967@gmail.com \
--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