1 |
>>>>> On Fri, 15 Jan 2010, Jorge Manuel B S Vicetto wrote: |
2 |
|
3 |
> - From the alternatives, /var/lib/layman doesn't sound right. |
4 |
|
5 |
The FHS (which we don't always obey, but in cases like this it's |
6 |
useful as a guideline) says about /var/lib: "This hierarchy holds |
7 |
state information pertaining to an application or the system. State |
8 |
information is data that programs modify while they run, and that |
9 |
pertains to one specific host." |
10 |
|
11 |
IMHO that doesn't fit layman's usage case. |
12 |
|
13 |
> If /var/cache/layman doesn't work, |
14 |
|
15 |
It doesn't, since the data cannot be locally (i.e. off-line) |
16 |
regenerated. |
17 |
|
18 |
> what about /var/spool/layman instead? |
19 |
|
20 |
Looks like it's the best location available in /var. |
21 |
|
22 |
But by analogy, layman should store things in the same hierarchy where |
23 |
the portage tree is, and that is under /usr. What was wrong with the |
24 |
original location /usr/portage/local? |
25 |
|
26 |
Ulrich |