From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Question about compilation
Date: Sat, 8 Feb 2025 23:28:27 -0600 [thread overview]
Message-ID: <d8a29bce-a484-c0b5-df4f-3b16e60b6746@gmail.com> (raw)
In-Reply-To: <4888c237-2277-4b3b-87d7-babff3d203e4@gentoo.org>
Matt Jolly wrote:
> Hi Dale,
>
> On 9/2/25 10:20, Dale wrote:
>
>> Would that survive a full reboot? I'm asking about a regular desktop
>> top system. It's rare but sometimes I am doing updates and have a
>> power failure and have to shutdown until power comes back. I've
>> always just done a emerge --resume but that starts any unfinished
>> emerges from scratch. Just curious if this would work. If I can
>> remember to do it if it does. ;-)
>
> Provided that your /var/tmp/portage isn't a tmpfs this will survive
> reboots and enable you to use `sudo ebuild foo-1.2.3 ebuild merge`
> to continue for _that package only_.
>
> The rest of the emerge will need to be restarted and the depgraph
> recalculated to finish whatever upgrade you were doing.
>
> If it's something big like Chromium though, by all means use
> `ebuild` to save a bunch of time - it's a lot better than
> global `ccache`. :)
>
> Cheers,
>
> Matt
>
>
Oops. I didn't think about it being on tmpfs. Given I have 128GBs of
memory now, I have a lot on tmpfs. So, after a reboot, it would be gone
anyway. Still, it would be nice if emerge had this feature, especially
for some of the big ones. My big ones are LOo, Firefox and that qtweb
thing. Last one being the largest.
Worth a thought. ;-)
Dale
:-) :-)
next prev parent reply other threads:[~2025-02-09 5:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-08 14:47 [gentoo-user] Question about compilation Jacques Montier
2025-02-08 19:00 ` Filip Kobierski
2025-02-08 23:07 ` Jack
2025-02-09 0:11 ` Michael
2025-02-09 0:20 ` Dale
2025-02-09 0:23 ` Matt Jolly
2025-02-09 5:28 ` Dale [this message]
2025-02-16 17:22 ` Wols Lists
2025-02-16 19:12 ` Dale
2025-02-09 0:46 ` [gentoo-user] " Nuno Silva
2025-02-09 10:23 ` [gentoo-user] " MLR
2025-02-09 14:36 ` Håkon Alstadheim
2025-02-09 16:44 ` Jacques Montier
2025-02-09 17:06 ` Michael
2025-02-09 17:22 ` Jacques Montier
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=d8a29bce-a484-c0b5-df4f-3b16e60b6746@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