Gentoo Archives: gentoo-dev

From: Duncan <1i5t5.duncan@×××.net>
To: gentoo-dev@l.g.o
Subject: [gentoo-dev] Re: [rfc] layman storage location (again)
Date: Sat, 16 Jan 2010 03:09:07
Message-Id: pan.2010.01.16.03.07.27@cox.net
In Reply to: Re: [gentoo-dev] [rfc] layman storage location (again) by Mike Frysinger
1 Mike Frysinger posted on Fri, 15 Jan 2010 20:45:49 -0500 as excerpted:
2
3 > On Friday 15 January 2010 20:24:38 Sebastian Pipping wrote:
4 >> On 01/16/10 00:33, Jorge Manuel B. S. Vicetto wrote:
5 >> > - From the alternatives, /var/lib/layman doesn't sound right. If
6 >> > /var/cache/layman doesn't work, what about /var/spool/layman instead?
7 >>
8 >> Okay, how about
9 >>
10 >> /var/spool/layman
11 >>
12 >> then? Any objections?
13 >
14 > /var/spool/ is a terrible idea -- these are not jobs being queued
15 > waiting to be processed by a daemon and then removed.
16 >
17 > if you want to keep all of layman's stuff together, then about your only
18 > option is to create your own tree at like /var/layman/. the better idea
19 > though would be to split your stuff along the proper lines.
20 >
21 > cache files = /var/cache/layman/
22 > config files = /etc/layman/
23
24 This looks pretty good to me, too.
25
26 1) Don't mess with /usr/local/, that's reserved for local use.
27
28 (FWIW, it's only because I'm lazy and use single-letter "p" for my
29 portage dirs, that you didn't clash with anything I do, here. But I
30 /was/ wondering what the layman dir was doing in my local files!)
31
32 2) /etc/ (/etc/layman/, or as I use, /etc/portage/layman, but some folks
33 may not like that) for config, but do keep in mind that some folks keep
34 / (and thus /etc) read-only during normal operation. Thus, you can't
35 properly put your runtime-updated files there.
36
37 (It could of course be argued that layman updates should be done with
38 gentoo tree updates, thus, during package manager updates, which aren't
39 really normal operation since Gentoo at least depends on / and /etc being
40 writable for package updates, but then you lose the flexibility of being
41 able to update layman on its own, during otherwise normal operation.)
42
43 3) /var/spool/ isn't right either, because as someone else mentioned,
44 these aren't files spooled for use by some daemon and then deletion.
45
46 4) That leaves some place in /var/cache or /var/lib, or possibly /usr
47 (taking a cue from Gentoo's default /usr/portage), for your
48 runtime-updated files.
49
50 I don't personally much care which of those are used, but /usr/ itself
51 may be read-only mounted as well during normal operation (with
52 /usr/portage/ either on a different mountpoint, or the local gentoo tree
53 stored elsewhere), so I'd suggest, unless you wish to use
54 /usr/portage/layman, you don't use /usr/ at all, which leaves /var/lib/
55 or /var/cache/.
56
57 --
58 Duncan - List replies preferred. No HTML msgs.
59 "Every nonfree program has a lord, a master --
60 and if you use the program, he is your master." Richard Stallman