From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.54) id 1FRN3O-00001e-U4 for garchives@archives.gentoo.org; Thu, 06 Apr 2006 05:29:11 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.6/8.13.5) with SMTP id k365T1Y5030107; Thu, 6 Apr 2006 05:29:01 GMT Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.199]) by robin.gentoo.org (8.13.6/8.13.5) with ESMTP id k365RCaB026860 for ; Thu, 6 Apr 2006 05:27:13 GMT Received: by zproxy.gmail.com with SMTP id j2so62374nzf for ; Wed, 05 Apr 2006 22:27:12 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:to:subject:references:message-id:date:from:content-type:mime-version:content-transfer-encoding:in-reply-to:user-agent; b=k/nWwiycA/G5qKf0VeMFBxFnuui/TaviGIseqi2TWvw0LFC8lkwO+VSrkm8f6iMf1/+dhJwdaiLmsp3F0bAf76q1kidVLUo2IpFd7jH4f0YOPl0gYbCnJ60P9IWvaraGaMrarbF4BChwzkhCtqQUmMG1MpOd4L/EtDv390Ne0bY= Received: by 10.37.18.45 with SMTP id v45mr522059nzi; Wed, 05 Apr 2006 22:27:12 -0700 (PDT) Received: from tesla.aether ( [203.25.40.66]) by mx.gmail.com with ESMTP id r15sm104624nza.2006.04.05.22.27.11; Wed, 05 Apr 2006 22:27:12 -0700 (PDT) To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] emerge resume list References: <44349F59.4020603@gentoo.org> Message-ID: Date: Thu, 06 Apr 2006 15:26:55 +1000 From: evader Content-Type: text/plain; format=flowed; delsp=yes; charset=utf-8 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Transfer-Encoding: 8bit In-Reply-To: <44349F59.4020603@gentoo.org> User-Agent: Opera M2/8.52 (Linux, build 1631) X-Archives-Salt: f0dde894-f943-4972-8e50-3865f83d60a5 X-Archives-Hash: 98e58677a85cd02de9f480ba7fdfadca Hi, Further to my email before, a quick hack in the emerge script somewhere here should fix it: # We're resuming. print green("*** Resuming merge...") emergelog(" *** Resuming merge...") mymergelist=portage.mtimedb["resume"]["mergelist"][:] if ("--skipfirst" in myopts) and mymergelist: del portage.mtimedb["resume"]["mergelist"][0] del mymergelist[0] for bigkey in mymergelist: (pkgtype, root, cpv, action) = bigkey if pkgtype == "binary" and not portage.db["/"]["bintree"].dbapi.match("="+cpv) or \ pkgtype == "ebuild" and not portage.db["/"]["porttree"].dbapi.xmatch("match-all", "="+cpv): This is the first time I've looked at so I'll see how I go. Any tips? evader On Thu, 06 Apr 2006 14:55:53 +1000, Alec Warner wrote: > 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