From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 5A4DA1381F3 for ; Thu, 20 Dec 2012 11:41:14 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id BCAAB21C034; Thu, 20 Dec 2012 11:41:00 +0000 (UTC) Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 5DD6D21C046 for ; Thu, 20 Dec 2012 11:40:07 +0000 (UTC) Received: by mail-bk0-f44.google.com with SMTP id w11so1567033bku.3 for ; Thu, 20 Dec 2012 03:40:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:date:from:to:subject:message-id:in-reply-to:references :organization:x-mailer:mime-version:content-type :content-transfer-encoding; bh=U/mKjKTCeAg6XfSyB3rUfsefzG4vfXKSvjm0QrO5sj4=; b=cXFZ2hAJb55VwpLdvHYYMpfgCLoFV0M4b1J9RAVhQGPTy5uqRI7RnGDRva9vP+t20D PTs1/56qreCJnt/pOYN6SynMoi9syNevVg43NN/0hDH3RhQkNtqwxLeufHOP2a8R/dZE kacR78RBL6tlZksT0JMUDMQgnZBYhFSMe0THUGGij6G/Q0SQhrDXLd3o5Tuc7QBr53wc HdFrvz48fZlbB9My1CTZ+0DMsVEXzfnTGAJPEGcNLaWUsZ0W2LxnvyZovgI5TntiGx85 BOVC75jbToLc0xDbUt3SlHrX1d9gDb2zbEU7l4tNb7Q/3JPzDZlvvBao2yE4vRnpJpwx nGew== X-Received: by 10.204.150.137 with SMTP id y9mr4385565bkv.103.1356003605898; Thu, 20 Dec 2012 03:40:05 -0800 (PST) Received: from khamul.example.com (dustpuppy.is.co.za. [196.14.169.11]) by mx.google.com with ESMTPS id 18sm6757435bkv.0.2012.12.20.03.40.03 (version=SSLv3 cipher=OTHER); Thu, 20 Dec 2012 03:40:04 -0800 (PST) Date: Thu, 20 Dec 2012 13:36:27 +0200 From: Alan McKinnon To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Moving our/portage stuff to var Message-ID: <20121220133627.49101bd3@khamul.example.com> In-Reply-To: <50D23D88.70600@gentoo.org> References: <20121218222046.3f57a21f@brain.lan> <7546589.4cZ9dCx8p9@bart> <50D1B94F.3080201@flameeyes.eu> <20689.50332.706030.896119@a1i15.kph.uni-mainz.de> <50D1C79C.3000809@flameeyes.eu> <20121220000145.0fc3f6c6@khamul.example.com> <50D23D88.70600@gentoo.org> Organization: Internet Solutions X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.14; x86_64-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 545e564f-1409-45fc-8b06-33614336662e X-Archives-Hash: ad8c7434baba32d0ab117b4726c1e328 On Wed, 19 Dec 2012 14:19:52 -0800 Zac Medico wrote: > On 12/19/2012 02:01 PM, Alan McKinnon wrote: > > On Wed, 19 Dec 2012 14:56:44 +0100 > > Diego Elio Petten=F2 wrote: > >=20 > >> Just mv /usr/portage /var/portage ? FFS no. Among other things, as > >> many said before, we should really take distfiles out of the tree > >> itself, and packages the same. And I don't want /var/packages > >> or /var/distfiles at all. > >=20 > > If we are going to move distfiles out of the tree into, what are the > > odds of getting /some/path/portage/local to move somewhere else too? >=20 > What program uses this "local" directory? It's not used directly by > portage itself, though portage has an exclude for it in the default > PORTAGE_RSYNC_OPTS setting > (in /usr/share/portage/config/make.globals). It goes back a long time, and is basically a poor man's local overlay without having to use layman. As I understand it, portage will treat the directory like any other when looking for ebuilds and resolving deps, but exclude it from a sync. >=20 > > That one has irked me for ages, its the one thing left on my systems > > that stops the local tree dir being an exact replica of the upstream > > master. >=20 > For portage's defaults, I won't settle for anything less than having > them all refer to separate directories which are *not* nested within > one other. These are the current default settings which violate my > requirements: >=20 > PORTDIR=3D/usr/portage > DISTDIR=3D${PORTDIR}/distfiles > PKGDIR=3D${PORTDIR}/packages > RPMDIR=3D${PORTDIR}/rpm /usr/portage/local has the taste feel and smell of a hacky workaround: shove a directory in the tree and exclude it from sync. I suspect the best solution all round is to move all support for local overlays into layman. I'd be happy with that. Probably make the portage code cleaner too. --=20 Alan McKinnon alan.mckinnon@gmail.com