From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gentoo-dev+bounces-85219-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by finch.gentoo.org (Postfix) with ESMTPS id D703E138334
	for <garchives@archives.gentoo.org>; Wed, 11 Jul 2018 16:19:48 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id D5541E0805;
	Wed, 11 Jul 2018 16:19:42 +0000 (UTC)
Received: from mail-ed1-x542.google.com (mail-ed1-x542.google.com [IPv6:2a00:1450:4864:20::542])
	(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
	(No client certificate requested)
	by pigeon.gentoo.org (Postfix) with ESMTPS id 492F1E07F6
	for <gentoo-dev@lists.gentoo.org>; Wed, 11 Jul 2018 16:19:42 +0000 (UTC)
Received: by mail-ed1-x542.google.com with SMTP id x5-v6so15945456edr.0
        for <gentoo-dev@lists.gentoo.org>; Wed, 11 Jul 2018 09:19:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=scriptkitty-com.20150623.gappssmtp.com; s=20150623;
        h=mime-version:sender:in-reply-to:references:from:date:message-id
         :subject:to;
        bh=IUDLbcYc/X6MPkpluU9C1YPMBT5LUyc7mpmfm8i94w0=;
        b=gX1jqt6NebuE1e6jih0hRqgB46q5BZQFhi8d83M3KtuKU7qwmdrdu8Wy3JJNXhfJEj
         jcxuBUvR+5ARgacSbAP5wIvm9K/6wE+v9rE/JatR/rw0YfqexeL/a+TUKRrRaaQntJg8
         tR3ODkyBgdn5ZDkLIAF+4AbzObEGpBQIniRorx/1z6vwsuyOhUSwLxkeZvnSfnpHHsXT
         6JyPMqSU58ptSBaG/i0Yd5U8cdDePVMIfGFe+yjOC9HAeXGgVcncdreUCFDhjw4T3RsM
         Te/NFFnYVoVHdO2CdghJ05rc9oMdh3U5uohx83xwGOXVU86lDb/3dnTN5/EoQWrzysWZ
         KarA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:sender:in-reply-to:references:from
         :date:message-id:subject:to;
        bh=IUDLbcYc/X6MPkpluU9C1YPMBT5LUyc7mpmfm8i94w0=;
        b=QvtWqpdf91zwEIFTI6Blr7a9u3kYGgG8cKcu0f2GMxw0uYB9Cz9WQKulzHbDBLHyCm
         EtJx8aFq/D/Uzu/Uw4IlvcLL5PqdTuzfImsa2c3QuKamna1VReKanxe9ImUwm6MkuOF0
         sVMA3SCp3oQ9AZmIqHnNdg9a6MOZdhiG5xKigs61rx1aFFLuQN1QOs2yjDZjy7nH1+mq
         FRyiOVgWF+igdsGUc2yJ48AunBJydVMHwizHYckWO/yBbied+yRQMmh+QqGYVXObECPR
         UiYfMWuufiH3mbspFCkOrxBO22zZH17yu/8+YgBHssp3V18ROL0gc8B4VeQJ6scKhSrd
         ngtw==
X-Gm-Message-State: AOUpUlHDry84pQuywg6PkddNeRPBsosZ+dQI37EClbSKT5toQ/ZfG98M
	92vFyQk32DwpnxGB07Udznu3Yeot7cqS1angEyF3xf87
X-Google-Smtp-Source: AAOMgpeeHeM/Ph8xuTuW8d+hUt7nskhF+4TT8tRBIUwh+FnM3XaxA2qfvuZJBcOSKanMzpCnLIL0efGBxC9tq8Rv3m4=
X-Received: by 2002:a50:8dcb:: with SMTP id s11-v6mr11722366edh.86.1531325980428;
 Wed, 11 Jul 2018 09:19:40 -0700 (PDT)
Precedence: bulk
List-Post: <mailto:gentoo-dev@lists.gentoo.org>
List-Help: <mailto:gentoo-dev+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-dev+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
X-BeenThere: gentoo-dev@lists.gentoo.org
Reply-to: gentoo-dev@lists.gentoo.org
MIME-Version: 1.0
Sender: antarus@scriptkitty.com
Received: by 2002:a17:906:d0c4:0:0:0:0 with HTTP; Wed, 11 Jul 2018 09:19:39
 -0700 (PDT)
X-Originating-IP: [2620:0:1003:510:3569:b826:602f:b690]
In-Reply-To: <CAGfcS_kOJEqF-UMCNs_U6H-fd0JuJyNbpDhptmQvqriWSYPKBw@mail.gmail.com>
References: <20180709172136.GA17068@linux1.home> <1531161811.1159.13.camel@gentoo.org>
 <20180709201113.GB17593@linux1.home> <1531167218.1159.15.camel@gentoo.org>
 <CAGfcS_ke5Esm_3JS_1bzSLv=ZjabdmBnv_tA-nJkt4+rKqGTww@mail.gmail.com>
 <20180709211410.GA17986@linux1.home> <2f7c8b18-8c5d-2931-14a7-9d6d1e00526d@gentoo.org>
 <29b55e16-bb2e-5a98-13e2-e1482441b417@gentoo.org> <8b47a97d-37be-652a-0298-7e7082506b53@iee.org>
 <50aa6222-d97c-6fd0-0884-23b27f494135@gentoo.org> <20180710200923.GA21918@linux1.home>
 <88409c1e-eb34-dad8-c524-2b44de5bc91b@iee.org> <5f2b3a86-c7d5-f588-5ea3-4c13055d8324@gentoo.org>
 <CAHY5Mefj6OACdTJchRwccM8aNUr1QYw1_9Jd-9gGLgk8cK0X4A@mail.gmail.com>
 <CAGDaZ_oS9WRxYcDHbqr4cC4X0cKBJPJogLGWQ1_7-WKPDp9UbQ@mail.gmail.com> <CAGfcS_kOJEqF-UMCNs_U6H-fd0JuJyNbpDhptmQvqriWSYPKBw@mail.gmail.com>
From: Alec Warner <antarus@gentoo.org>
Date: Wed, 11 Jul 2018 12:19:39 -0400
X-Google-Sender-Auth: IGCSI9KLicZrlcw0q2qn0w6vbkA
Message-ID: <CAAr7Pr-iqW-w15F-+VZZK6-6h58r8oC_o57gHpds8kw6gDQRAw@mail.gmail.com>
Subject: Re: [gentoo-dev] rfc: moving default location of portage tree
To: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Content-Type: multipart/alternative; boundary="0000000000001962a90570bb9d5e"
X-Archives-Salt: b4b1dd34-e77e-47f4-80cc-faa56ceeffdd
X-Archives-Hash: 4f23191ce9ba3711ac53131c01176ce3

--0000000000001962a90570bb9d5e
Content-Type: text/plain; charset="UTF-8"

On Wed, Jul 11, 2018 at 11:56 AM, Rich Freeman <rich0@gentoo.org> wrote:

> On Wed, Jul 11, 2018 at 11:36 AM Raymond Jennings <shentino@gmail.com>
> wrote:
> >
> > I do think it would be a wise idea to "grandfather" the current layout
> > for awhile.
> >
>
> I don't see why we would ever stop supporting it, at least in general.
> Maybe if some day somebody had a solution for a read-only /usr with
> signature checking that might require portage to be mounted elsewhere,
> but I don't ever see that becoming the default.
>
> Portage just looks for the repository where you tell it to.  If you
> tell it that the repository is in /var, it will use it.  If you put it
> in /tmp, that's fine too.
>

+1 to this. The challenge (in moving it) is that its been "/usr/portage"
for a long time so many tools
may have hard coded this location; as opposed to querying portage for where
the tree is, e.g.:

PORTDIR=$(portageq get_repo_path / gentoo)

-A


> This is just about the default, which should follow FHS.  The case of
> separate mounts is exactly why /usr is a bad spot - the access
> patterns for something like the repository have far more in common
> with /var than /usr.
>
-- 
> Rich
>
>

--0000000000001962a90570bb9d5e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Wed, Jul 11, 2018 at 11:56 AM, Rich Freeman <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:rich0@gentoo.org" target=3D"_blank">rich0@gentoo.org</a>&gt=
;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D"">On Wed, =
Jul 11, 2018 at 11:36 AM Raymond Jennings &lt;<a href=3D"mailto:shentino@gm=
ail.com">shentino@gmail.com</a>&gt; wrote:<br>
&gt;<br>
&gt; I do think it would be a wise idea to &quot;grandfather&quot; the curr=
ent layout<br>
&gt; for awhile.<br>
&gt;<br>
<br>
</span>I don&#39;t see why we would ever stop supporting it, at least in ge=
neral.<br>
Maybe if some day somebody had a solution for a read-only /usr with<br>
signature checking that might require portage to be mounted elsewhere,<br>
but I don&#39;t ever see that becoming the default.<br>
<br>
Portage just looks for the repository where you tell it to.=C2=A0 If you<br=
>
tell it that the repository is in /var, it will use it.=C2=A0 If you put it=
<br>
in /tmp, that&#39;s fine too.<br></blockquote><div><br></div><div>+1 to thi=
s. The challenge (in moving it) is that its been &quot;/usr/portage&quot; f=
or a long time so many tools</div><div>may have hard coded this location; a=
s opposed to querying portage for where the tree is, e.g.:</div><div><br></=
div><div>PORTDIR=3D$(portageq get_repo_path / gentoo)</div><div><br></div><=
div>-A</div><div><br></div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
This is just about the default, which should follow FHS.=C2=A0 The case of<=
br>
separate mounts is exactly why /usr is a bad spot - the access<br>
patterns for something like the repository have far more in common<br>
with /var than /usr.=C2=A0<br></blockquote><blockquote class=3D"gmail_quote=
" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><=
span class=3D"HOEnZb"><font color=3D"#888888">-- <br>
Rich<br>
<br>
</font></span></blockquote></div><br></div></div>

--0000000000001962a90570bb9d5e--