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 1PPMpy-0004vd-Bn for garchives@archives.gentoo.org; Sun, 05 Dec 2010 22:13:42 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 3F00BE076F; Sun, 5 Dec 2010 22:13:33 +0000 (UTC) Received: from a1iwww1.kph.uni-mainz.de (a1iwww1.kph.uni-mainz.de [134.93.134.1]) by pigeon.gentoo.org (Postfix) with ESMTP id C1F57E076F for ; Sun, 5 Dec 2010 22:13:32 +0000 (UTC) Received: from a1i15.kph.uni-mainz.de (a1i15.kph.uni-mainz.de [134.93.134.92]) by a1iwww1.kph.uni-mainz.de (8.14.0/8.13.4) with ESMTP id oB5MDUZk023868; Sun, 5 Dec 2010 23:13:30 +0100 Received: from a1i15.kph.uni-mainz.de (localhost [127.0.0.1]) by a1i15.kph.uni-mainz.de (8.14.3/8.14.2) with ESMTP id oB5MDUYC011832; Sun, 5 Dec 2010 23:13:30 +0100 Received: (from ulm@localhost) by a1i15.kph.uni-mainz.de (8.14.4/8.14.4/Submit) id oB5MDUP4011829; Sun, 5 Dec 2010 23:13:30 +0100 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Package Manager Specification discussions X-BeenThere: gentoo-pms@gentoo.org X-BeenThere: gentoo-pms@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <19708.3722.816939.875731@a1i15.kph.uni-mainz.de> Date: Sun, 5 Dec 2010 23:13:30 +0100 To: Ciaran McCreesh Cc: gentoo-pms@lists.gentoo.org Subject: Re: [gentoo-pms] Variancy? In-Reply-To: <20101205220627.64452d13@snowcone> References: <19708.2662.412210.696119@a1i15.kph.uni-mainz.de> <20101205220627.64452d13@snowcone> X-Mailer: VM 8.1.1 under 23.2.1 (x86_64-pc-linux-gnu) From: Ulrich Mueller X-Archives-Salt: ab45d7b1-588e-4982-b610-677ee1faf6af X-Archives-Hash: 045b4a2202309bc6f0eee062325de3b9 >>>>> On Sun, 5 Dec 2010, Ciaran McCreesh wrote: > That whole section was written before Portage got parallel jobs > support, and was based around what ebuilds were actually doing. > Portage's parallel jobs break those rules, and this has caused all > kinds of weirdness. > The implications are *supposed* to be that if you want to do parallel > builds, you build binary packages in parallel (being sure to only run > one lot of pkg_ functions at once), and then install those binary > packages (the usual way, so rerunning pkg_setup) serially. > Instead, Portage just installs directly, and has a whole load of > convoluted hacks to try to avoid breakage. These don't actually work, > but the bugs are hidden often enough that you can often go for quite a > long time before you end up screwing your system up... In particular, > Portage assumes that if a and b aren't in any way dependent upon each > other, then they're not going to do anything to / that's going to break > the other one, which isn't true. Thank you for your quick response, but this doesn't answer my questions: >> Why is the second item needed? Changes to DISTDIR don't alter other >> packages, so aren't they covered by the first item anyway? Or do I >> misunderstand the first item's first sentence? >> Which of the following examples count as "variancy"? >> - Calling enewuser() in pkg_setup, >> - Removing orphan files in pkg_setup, >> - Calling pkg_pretend. Ulrich