public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alec Warner <antarus@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] emerge resume list
Date: Thu, 06 Apr 2006 00:55:53 -0400	[thread overview]
Message-ID: <44349F59.4020603@gentoo.org> (raw)
In-Reply-To: <op.s7kieaif24azpy@tesla.aether>

evader wrote:
> Hi,
> 
> I'm not sure if this is the correct list to send this too, but it is
> the  only gentoo one I am currently subscribed to.
> 
> When I do an emerge -e world where is the list of files to be merged 
> stored? For example if I break an emerge, and want to resume later from
> a  different position, can I edit the packages to be emerged list so I
> don't  have to do emerge --resume --skipfirst constantly?
> 
> Thanks,
> 
> evader

The list is stored in a small database file in /var/cache/edb/mtimedb

It is a binary file full of pickled python objects.  I was actually
poking around it and thought about writing a tool.  I will commit more
time to it if you are interested; although be warned that editing things
in that file is not particularly recommended.  The dependency resolution
 for the packages in the list is done and the list is created.  Removing
items from it could cause packages to not build, and the dependency tree
to essentially be broken for that list.

Also, portage questions are generally well received at
gentoo-portage-dev@gentoo.org, or on IRC: irc.freenode.net #gentoo-portage.

-Alec Warner
-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2006-04-06  4:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-06  3:52 [gentoo-dev] emerge resume list evader
2006-04-06  4:55 ` Alec Warner [this message]
2006-04-06  5:08   ` evader
2006-04-06  5:26   ` evader
2006-04-06 13:48 ` Jeroen Roovers
2006-04-06 14:35 ` Albert W. Hopkins

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=44349F59.4020603@gentoo.org \
    --to=antarus@gentoo.org \
    --cc=gentoo-dev@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