1 |
On Fri, Jul 27, 2018 at 1:40 AM, Michał Górny <mgorny@g.o> wrote: |
2 |
> Dnia 27 lipca 2018 10:32:17 CEST, Ulrich Mueller <ulm@g.o> napisał(a): |
3 |
>>>>>>> On Thu, 19 Jul 2018, Chí-Thanh Christopher Nguyễn wrote: |
4 |
>> |
5 |
>>>> Users must never need to modify files in /var/lib to configure a |
6 |
>>>> package's operation, and _the_specific_file_hierarchy_ used to |
7 |
>>>> store the data _must_not_be_ _exposed_ to regular users." |
8 |
>> |
9 |
>>> One small note, while it is never needed to modify, skel.ebuild |
10 |
>>> would then be a file that is meant to be accessed by users in |
11 |
>>> /var/lib if your proposal is realized. |
12 |
>> |
13 |
>>That's one of the reasons why the proposal prefers /var/db. The other |
14 |
>>reason is existing usage in eselect-repository. |
15 |
>> |
16 |
>>>>>>> On Thu, 19 Jul 2018, Ulrich Mueller wrote: |
17 |
>> |
18 |
>>> In my understanding, a cache is typically an open collection of |
19 |
>>items. |
20 |
>>> Some subset of them can be deleted without much negative consequence, |
21 |
>>> and there may also be surplus items that are no longer necessary and |
22 |
>>> will be expired at some later time in order to reclaim disk space. |
23 |
>> |
24 |
>>> Nothing of this is true for an ebuild repository, which is a closed |
25 |
>>> collection of files: A single file cannot be discarded without |
26 |
>>> invalidating the whole repository. Also there cannot be any stray |
27 |
>>> files which would be expired later. Same as above, a single stray |
28 |
>>file |
29 |
>>> will invalidate all. |
30 |
>> |
31 |
>>> (A collection of binary packages may qualify as a cache though, by |
32 |
>>> this definition.) |
33 |
>> |
34 |
>>So, considering all the feedback from mailing list and IRC: |
35 |
>> |
36 |
>> /usr/portage -> /var/db/repos/gentoo |
37 |
>> /usr/portage/distfiles -> /var/cache{,/gentoo}/distfiles |
38 |
>> /usr/portage/packages -> /var/cache{,/gentoo}/binpkgs |
39 |
>> |
40 |
>>Open question: Should we have the additional "gentoo" path component |
41 |
>>for the ones in /var/cache? The tradeoff is between a path that is |
42 |
>>easier to type, or slightly easier usage if someone wants to NFS mount |
43 |
>>distfiles and binpkgs. |
44 |
> |
45 |
> 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. |
46 |
|
47 |
True, but trivially solvable by configuring like-hosts to share |
48 |
packages. Skylake packages go here, Sandybridge packages go here, etc. |
49 |
This is what I do. |