From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1PiRfZ-0003Vi-UH for garchives@archives.gentoo.org; Thu, 27 Jan 2011 13:13:50 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id AEEADE08F0; Thu, 27 Jan 2011 13:11:58 +0000 (UTC) Received: from mail-gw0-f53.google.com (mail-gw0-f53.google.com [74.125.83.53]) by pigeon.gentoo.org (Postfix) with ESMTP id 798BDE08F0 for ; Thu, 27 Jan 2011 13:11:58 +0000 (UTC) Received: by gwb10 with SMTP id 10so990774gwb.40 for ; Thu, 27 Jan 2011 05:11:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=vAdPft9m/sfc3Zw2odwzjsl3wGpl9lcEzeiJldkXHWo=; b=BSjLDiLpAswI/oZa/ON9VA9A3UbPsOFYzHrM9aTFAhNPQiiRGBbYx17amCnrYBAnbH hcQrLG9VvGQyxIOmgsph8zeeTrDmbnc5GJhy2vBAiUvHDmGoxmJ0ZS4At2UFiRRXhcAu SCTq0dE3bPh8hb47UJCHH2i3ZVL5Ct5LlBCYk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=JCfRzkM2jnjg3cHxGrKCA3AVPkqSJJ+CciqIOJbhn4HHYoF7wpp23wnh+3kyxQXeQU sjgwfgL5K4KW/sR1e4sUhPkjizm2vu0R/asRSXP15urzAp0MxuT0hn+5aV4XSECxIQr0 9RP/UEYSy2uFNzpwAccrz+pDW05FGTsQevWdI= Received: by 10.151.7.21 with SMTP id k21mr2768120ybi.306.1296133917865; Thu, 27 Jan 2011 05:11:57 -0800 (PST) Received: from [192.168.2.5] (adsl-0-95-40.jan.bellsouth.net [65.0.95.40]) by mx.google.com with ESMTPS id w24sm984828ybk.9.2011.01.27.05.11.49 (version=SSLv3 cipher=RC4-MD5); Thu, 27 Jan 2011 05:11:50 -0800 (PST) Message-ID: <4D416F12.8000202@gmail.com> Date: Thu, 27 Jan 2011 07:11:46 -0600 From: Dale User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20101212 Gentoo/2.0.11 SeaMonkey/2.0.11 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Re: Simultaneously emerging multiple packages with same dependencies References: <20110127100158.692bd251@digimed.co.uk> In-Reply-To: <20110127100158.692bd251@digimed.co.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: X-Archives-Hash: fd40ac3c0029a89db85b4f8bbb14f13b Neil Bothwick wrote: > On Thu, 27 Jan 2011 07:12:24 +0200, Nikos Chantziaras wrote: > > >>> I'm aware that portage uses locking mechanism before modifying 'world' >>> file, but what about the actual building process ? I'd expect emerge >>> to check if dependency package is already build/installed (or >>> currently being build by another instance) and just skip it in this >>> case, however I haven't tried it yet.. Can anybody shred some light >>> on this ? >>> >> You can try, but the second instance with simply block until the lock >> has been removed. >> > The lock is not there for the entire emerge, I have run two emerges at > the same time, such as when I needed to install something while a world > update is in progress. It is possible, but not recommended as a general > strategy. That's what --jobs is for. > > > I have done the same thing and as long as the dependencies don't clash, it works fine. However, if you start one emerge with a set of dependencies, then start another and they clash somewhere in the middle, portage has issues. That is where the locks would kick in I guess. I would also imagine that portage could emerge the same package twice too. If one instance of emerge doesn't know what the other instance has already done, then the second one could emerge it again. Doesn't emerge do all the calculating at the beginning and runs with that until the end? I am using the -j option for the first time now. I'm updating KDE. It seems to work fine. It doesn't scroll all the stuff like with a regular emerges but this new rig is so fast, I can't read it anyway. I did have a package to fail and it spit out the error for me to read. I agree, using --jobs is the best way to do this. It works really well if you have a fast multi-core CPU. I wish I had got me a 6 core one now. ;-) Dale :-) :-)