Gentoo Archives: gentoo-dev

From: Matt Turner <mattst88@g.o>
To: gentoo development <gentoo-dev@l.g.o>
Subject: Re: [gentoo-dev] rfc: moving default location of portage tree (was: [gentoo-project] Call for agenda items - Council meeting 2018-07-29)
Date: Sun, 29 Jul 2018 19:56:51
Message-Id: CAEdQ38H55b20kXrUGo6nJ1Xq7-pQs1pheRov2aSDHii_8cfQBA@mail.gmail.com
In Reply to: Re: [gentoo-dev] rfc: moving default location of portage tree (was: [gentoo-project] Call for agenda items - Council meeting 2018-07-29) by Ulrich Mueller
1 On Fri, Jul 27, 2018 at 1:32 AM, Ulrich Mueller <ulm@g.o> wrote:
2 >>>>>> On Thu, 19 Jul 2018, Chí-Thanh Christopher Nguyễn wrote:
3 >
4 >>> Users must never need to modify files in /var/lib to configure a
5 >>> package's operation, and _the_specific_file_hierarchy_ used to
6 >>> store the data _must_not_be_ _exposed_ to regular users."
7 >
8 >> One small note, while it is never needed to modify, skel.ebuild
9 >> would then be a file that is meant to be accessed by users in
10 >> /var/lib if your proposal is realized.
11 >
12 > That's one of the reasons why the proposal prefers /var/db. The other
13 > reason is existing usage in eselect-repository.
14 >
15 >>>>>> On Thu, 19 Jul 2018, Ulrich Mueller wrote:
16 >
17 >> In my understanding, a cache is typically an open collection of items.
18 >> Some subset of them can be deleted without much negative consequence,
19 >> and there may also be surplus items that are no longer necessary and
20 >> will be expired at some later time in order to reclaim disk space.
21 >
22 >> Nothing of this is true for an ebuild repository, which is a closed
23 >> collection of files: A single file cannot be discarded without
24 >> invalidating the whole repository. Also there cannot be any stray
25 >> files which would be expired later. Same as above, a single stray file
26 >> will invalidate all.
27 >
28 >> (A collection of binary packages may qualify as a cache though, by
29 >> this definition.)
30 >
31 > So, considering all the feedback from mailing list and IRC:
32 >
33 > /usr/portage -> /var/db/repos/gentoo
34 > /usr/portage/distfiles -> /var/cache{,/gentoo}/distfiles
35 > /usr/portage/packages -> /var/cache{,/gentoo}/binpkgs
36 >
37 > Open question: Should we have the additional "gentoo" path component
38 > for the ones in /var/cache? The tradeoff is between a path that is
39 > easier to type, or slightly easier usage if someone wants to NFS mount
40 > distfiles and binpkgs.
41
42 That proposal has by vote of support. No strong preference on whether
43 to include gentoo/ or not. It's one NFS mount vs two so not a big deal
44 either way.

Replies