From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1NVz2B-0007bH-70 for garchives@archives.gentoo.org; Sat, 16 Jan 2010 03:09:07 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 8DE74E06F3; Sat, 16 Jan 2010 03:08:03 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 481E9E06F3 for ; Sat, 16 Jan 2010 03:08:03 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id E343767E83 for ; Sat, 16 Jan 2010 03:08:02 +0000 (UTC) X-Virus-Scanned: amavisd-new at gentoo.org X-Spam-Score: -2.555 X-Spam-Level: X-Spam-Status: No, score=-2.555 required=5.5 tests=[AWL=0.044, BAYES_00=-2.599] Received: from smtp.gentoo.org ([127.0.0.1]) by localhost (smtp.gentoo.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XACguJY3Jdzd for ; Sat, 16 Jan 2010 03:07:56 +0000 (UTC) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTP id B359C67DE7 for ; Sat, 16 Jan 2010 03:07:54 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.50) id 1NVz0u-0007cE-EY for gentoo-dev@gentoo.org; Sat, 16 Jan 2010 04:07:48 +0100 Received: from ip68-231-22-224.ph.ph.cox.net ([68.231.22.224]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 16 Jan 2010 04:07:48 +0100 Received: from 1i5t5.duncan by ip68-231-22-224.ph.ph.cox.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 16 Jan 2010 04:07:48 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-dev@lists.gentoo.org From: Duncan <1i5t5.duncan@cox.net> Subject: [gentoo-dev] Re: [rfc] layman storage location (again) Date: Sat, 16 Jan 2010 03:07:26 +0000 (UTC) Message-ID: References: <4B50C3B4.5050604@gentoo.org> <4B50FB3B.60506@gentoo.org> <4B511556.4080409@gentoo.org> <201001152046.00963.vapier@gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: ip68-231-22-224.ph.ph.cox.net User-Agent: Pan/0.133 (House of Butterflies) Sender: news Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 9e9a4fc6-a67d-4eb3-acbc-da22c76e2b92 X-Archives-Hash: 98079d83689256feaf5e95da4e2eb7f7 Mike Frysinger posted on Fri, 15 Jan 2010 20:45:49 -0500 as excerpted: > On Friday 15 January 2010 20:24:38 Sebastian Pipping wrote: >> On 01/16/10 00:33, Jorge Manuel B. S. Vicetto wrote: >> > - From the alternatives, /var/lib/layman doesn't sound right. If >> > /var/cache/layman doesn't work, what about /var/spool/layman instead= ? >>=20 >> Okay, how about >>=20 >> /var/spool/layman >>=20 >> then? Any objections? >=20 > /var/spool/ is a terrible idea -- these are not jobs being queued > waiting to be processed by a daemon and then removed. >=20 > if you want to keep all of layman's stuff together, then about your onl= y > option is to create your own tree at like /var/layman/. the better ide= a > though would be to split your stuff along the proper lines. >=20 > cache files =3D /var/cache/layman/ > config files =3D /etc/layman/ This looks pretty good to me, too. 1) Don't mess with /usr/local/, that's reserved for local use. (FWIW, it's only because I'm lazy and use single-letter "p" for my=20 portage dirs, that you didn't clash with anything I do, here. But I=20 /was/ wondering what the layman dir was doing in my local files!) 2) /etc/ (/etc/layman/, or as I use, /etc/portage/layman, but some folks=20 may not like that) for config, but do keep in mind that some folks keep / (and thus /etc) read-only during normal operation. Thus, you can't=20 properly put your runtime-updated files there. (It could of course be argued that layman updates should be done with=20 gentoo tree updates, thus, during package manager updates, which aren't=20 really normal operation since Gentoo at least depends on / and /etc being= =20 writable for package updates, but then you lose the flexibility of being=20 able to update layman on its own, during otherwise normal operation.) 3) /var/spool/ isn't right either, because as someone else mentioned,=20 these aren't files spooled for use by some daemon and then deletion. 4) That leaves some place in /var/cache or /var/lib, or possibly /usr=20 (taking a cue from Gentoo's default /usr/portage), for your runtime-updated files. I don't personally much care which of those are used, but /usr/ itself=20 may be read-only mounted as well during normal operation (with=20 /usr/portage/ either on a different mountpoint, or the local gentoo tree=20 stored elsewhere), so I'd suggest, unless you wish to use=20 /usr/portage/layman, you don't use /usr/ at all, which leaves /var/lib/=20 or /var/cache/. --=20 Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman