From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gentoo-dev+bounces-85182-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 44983138334
	for <garchives@archives.gentoo.org>; Mon,  9 Jul 2018 18:31:35 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id 690AAE089A;
	Mon,  9 Jul 2018 18:31:29 +0000 (UTC)
Received: from mail-pl0-f49.google.com (mail-pl0-f49.google.com [209.85.160.49])
	(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 EF2D6E083D
	for <gentoo-dev@lists.gentoo.org>; Mon,  9 Jul 2018 18:31:28 +0000 (UTC)
Received: by mail-pl0-f49.google.com with SMTP id m16-v6so6413610pls.11
        for <gentoo-dev@lists.gentoo.org>; Mon, 09 Jul 2018 11:31:28 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:references:in-reply-to:from:date
         :message-id:subject:to:cc;
        bh=AQwwPVPkS7IT+ivMto5bcGeAlS73SmGQDQCY0WbE5vg=;
        b=Pkotq6aSSi1mG9uh+9LrYb39c685FsbLEK5T4cvVFczx1Bj09q8EsDyHQl9VQDy2dc
         Ojtst2enviY3ygA8HHm2EWWwErhtMjVoeHekw4kH2EecDBnuS5fwBbpeTAgc5dZSE3aw
         VcELCCzVKyB239FCARmPQqNT8q+IbArBkUJKCZgMs/5Hfar5WiEdNbB5qmIHXIcNaJox
         OWsHzeqOA/9zFRs/PqO6LsI4KNswB725IiyNzAATiZrtIeERBUaA9f/UxwhDibpCa2dk
         RGFaJfvQ/Tsp8nZ/sK5pa5sCSBCr0xBFfZU0cHqHN98UuOXhJwZxC9I9E3M0Bv8+4uTj
         MmyA==
X-Gm-Message-State: APt69E3fOzc//mJxTzpTkzIctYEKGBo/xQRKvTGPJVsOE+1N+tafnzBk
	x4ISG7YXwAsmfbsb+wGg8Ziyjp3Iqg6ACA91qzILEA==
X-Google-Smtp-Source: AAOMgpc7pP2Rs6G2DrUHp/vWBnPbj5BVhCvhm7lz+XkvYgwL+XWqTemSi50RZDdu2yWgsSpLwWiyK6ba4bQhYvxIsho=
X-Received: by 2002:a17:902:8497:: with SMTP id c23-v6mr22129004plo.124.1531161087701;
 Mon, 09 Jul 2018 11:31:27 -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
References: <20180709172136.GA17068@linux1.home> <23363.40457.628259.180459@a1i15.kph.uni-mainz.de>
 <CAGfcS_mE0FscWQ7jZ1cEZf1GofhyUKbZ33ji9U5VhopeJjJpCA@mail.gmail.com> <d194def8-8143-7e9c-7bdf-52db17603e77@gentoo.org>
In-Reply-To: <d194def8-8143-7e9c-7bdf-52db17603e77@gentoo.org>
From: Rich Freeman <rich0@gentoo.org>
Date: Mon, 9 Jul 2018 14:31:15 -0400
Message-ID: <CAGfcS_=eM7mpx69tJRAsKT1EdZ8bgV=+G8PPW2h2vSVS0GybKw@mail.gmail.com>
Subject: Re: [gentoo-dev] rfc: moving default location of portage tree
To: johu@gentoo.org
Cc: gentoo-dev <gentoo-dev@lists.gentoo.org>
Content-Type: text/plain; charset="UTF-8"
X-Archives-Salt: a7c91a6f-1539-4cdd-ae61-f63af9229387
X-Archives-Hash: 47acd28c80753af8c2c636d3e01849cf

On Mon, Jul 9, 2018 at 2:11 PM Johannes Huber <johu@gentoo.org> wrote:
>
> Am 09.07.2018 um 20:05 schrieb Rich Freeman:
> > On Mon, Jul 9, 2018 at 1:40 PM Ulrich Mueller <ulm@gentoo.org> wrote:
> >>
> >>>>>>> On Mon, 9 Jul 2018, William Hubbs wrote:
> >>
> >>> is there a tracker for when the portage tree can be moved out of
> >>> /usr/portage by default?
> >>
> >>> If not, what is the status of us being able to do this?
> >>
> >> Please remind me, what was the plan for the new location?
> >> Somewhere under /var/db or /var/lib, IIRC?
> >>
> >
> > I'd also consider /var/cache here as well.  FHS specifically suggests
> > using it for web caches and the like (let's set aside the issue with
> > making that global), though for the most part it is more metadata
> > caching.  A key principle is that it can be wiped without loss of
> > data, and I think that is generally true for the repository since it
> > can be synced.
> >
> > Stuff in /var/lib can't be deleted without some kind of loss of
> > application state.  /var/db isn't in FHS, and I note that even mysql
> > sticks its stuff in /var/lib.
> >
>
> Imho it would make sense to split up portage files with this change.
> Move the tree (ebuilds, profiles etc) to /var/lib/... and the metadata
> cache to /var/db as it can be regenerated out of the tree.
>

Are you talking about the metadata that gets synced as part of the
repository?  Conceptually I like the idea of splitting it out, but IMO
the whole repository is really just one big cache, so keeping it
together since it always has to be consistent isn't a huge problem.

If you're talking about the stuff in /var/cache/edb, then that should
be separate from the repository, but should still be in cache.

I'd probably create /var/cache/portage, with subdirectories for
repositories (with a subdir for each one synced by portage), edb,
distfiles, and binary packages.
/var/cache/portage/repos/main
/var/cache/portage/repos/my-favorite-overlay
/var/cache/portage/distfiles
/var/cache/portage/edb

The stuff in /var/db/pkg should probably go in /var/lib/portage/pkg or
something like that, at least long-term.

-- 
Rich