1 |
On 01/18/10 01:38, Sebastian Pipping wrote: |
2 |
> On 01/17/10 21:31, Thilo Bangert wrote: |
3 |
>> /var/layman i dislike due to this sentence in the FHS: |
4 |
>> |
5 |
>> "Applications must generally not add directories to the top level of |
6 |
>> /var. Such directories should only be added if they have some system-wide |
7 |
>> implication[...]" |
8 |
> |
9 |
> [..] |
10 |
> |
11 |
> current ranking through my eyes: |
12 |
> |
13 |
> 1) /var/layman con: adds folder to /var, maybe should not |
14 |
> 2) /var/db/layman con: you tell me |
15 |
> 3) /var/lib/layman con: not really /var/lib-style data |
16 |
|
17 |
let me put the thoughts we collected so far to a decision. |
18 |
|
19 |
looking at /var shows, that not many application really dared to have a |
20 |
dedicated folder in /var directly: |
21 |
|
22 |
# find /var -maxdepth 1 -type d |
23 |
/var |
24 |
/var/tmp |
25 |
/var/lost+found |
26 |
/var/www |
27 |
/var/cache |
28 |
/var/spool |
29 |
/var/run |
30 |
/var/lock |
31 |
/var/db |
32 |
/var/gdm <-- gnome-base/gdm |
33 |
/var/lib |
34 |
/var/empty <-- net-misc/openssh |
35 |
/var/log |
36 |
/var/state |
37 |
|
38 |
after re-considering the requirements for /var/lib/layman the data in |
39 |
there can be host-specific (and therefore is not host-independent in |
40 |
general). i think it fits _well enough_ and to my impression it has |
41 |
less potential of turning out wrong than non-FHS /var/db: |
42 |
|
43 |
so /var/lib/layman is the new default. |
44 |
|
45 |
expect related commits to layman soon. |
46 |
|
47 |
|
48 |
|
49 |
sebastian |