Gentoo Archives: gentoo-dev

From: "Michał Górny" <mgorny@g.o>
To: gentoo-dev@l.g.o, Ulrich Mueller <ulm@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: Fri, 27 Jul 2018 08:41:00
Message-Id: 0FA12EA9-2CF9-43D6-A396-36F8FB24256F@gentoo.org
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 Dnia 27 lipca 2018 10:32:17 CEST, Ulrich Mueller <ulm@g.o> napisał(a):
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
18 >items.
19 >> Some subset of them can be deleted without much negative consequence,
20 >> and there may also be surplus items that are no longer necessary and
21 >> will be expired at some later time in order to reclaim disk space.
22 >
23 >> Nothing of this is true for an ebuild repository, which is a closed
24 >> collection of files: A single file cannot be discarded without
25 >> invalidating the whole repository. Also there cannot be any stray
26 >> files which would be expired later. Same as above, a single stray
27 >file
28 >> will invalidate all.
29 >
30 >> (A collection of binary packages may qualify as a cache though, by
31 >> this definition.)
32 >
33 >So, considering all the feedback from mailing list and IRC:
34 >
35 > /usr/portage -> /var/db/repos/gentoo
36 > /usr/portage/distfiles -> /var/cache{,/gentoo}/distfiles
37 > /usr/portage/packages -> /var/cache{,/gentoo}/binpkgs
38 >
39 >Open question: Should we have the additional "gentoo" path component
40 >for the ones in /var/cache? The tradeoff is between a path that is
41 >easier to type, or slightly easier usage if someone wants to NFS mount
42 >distfiles and binpkgs.
43
44 Note that NFS is not exactly clear cut here since binpkgs are not portable to different hosts, so you can have multiple variants of it.
45
46 >
47 >Ulrich
48
49
50 --
51 Best regards,
52 Michał Górny (by phone)

Replies