From: "vivo75@gmail.com" <vivo75@gmail.com>
To: gentoo-dev@lists.gentoo.org
Cc: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
Subject: Re: [gentoo-dev] Is /var/cache the right place for repositories?
Date: Mon, 24 Dec 2012 15:47:16 +0100 [thread overview]
Message-ID: <50D86AF4.6020005@gmail.com> (raw)
In-Reply-To: <20121224091119.2e08115f@googlemail.com>
Il 24/12/2012 10:11, Ciaran McCreesh ha scritto:
> On Mon, 24 Dec 2012 03:17:06 +0100
> Sebastian Pipping <sping@gentoo.org> wrote:
>> On 20.12.2012 19:14, Ciaran McCreesh wrote:
>>> The tree is a database. It belongs in /var/db/.
yes and no,
yes it contain data and executable needed to update gentoo system, in a
hierarchical and relational form
no, it's a cache of a remote database generally mantained from others.
Actually also the difference in importance between /var/db/pkg and
/????/ebuild_tree is very high.
Loose the pkg db and your best plan is to re-emerge the entire world,
provided you still have a copy of /var/lib/portage/world (or
equivalent), loose the latter and have a laugh.
To put those in the same category seem risky
Not that I personally care since everything gentoo related is kept in /g
on my systems, also this for various reason mainly because it's
something used to mantain a system and if maintainaince is not needed
it's very easy this way to remove.
>> I don't see /var/db in the latest release of the Filesystem Hierarchy
>> Standard:
>>
>> http://www.pathname.com/fhs/pub/fhs-2.3.html#THEVARHIERARCHY
>>
>> I would prefer something that blends with FHS.
> That's ok, Gentoo doesn't follow FHS.
>
And it's ok to "prefere" to stay near a standard and use it as a
guideline, for various reason, less difference with others and because a
bunch of people has already toughted on it, to name just two.
Raising to "MUST blend" would be indeed not beneficial.
Regards,
Francesco Riosa
next prev parent reply other threads:[~2012-12-24 14:48 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-20 17:27 [gentoo-dev] Is /var/cache the right place for repositories? Ulrich Mueller
2012-12-20 18:00 ` Ian Stakenvicius
2012-12-20 18:12 ` Ulrich Mueller
2012-12-20 18:19 ` [gentoo-dev] Keeping licenses around Ian Stakenvicius
2012-12-20 18:21 ` Diego Elio Pettenò
2012-12-20 20:25 ` Rich Freeman
2012-12-20 20:49 ` Rick "Zero_Chaos" Farina
2012-12-20 20:46 ` Zac Medico
2012-12-20 21:23 ` Rich Freeman
2012-12-20 22:33 ` Ulrich Mueller
2012-12-20 21:54 ` [gentoo-dev] Is /var/cache the right place for repositories? Chí-Thanh Christopher Nguyễn
2012-12-20 18:10 ` Alexandre Rostovtsev
2012-12-21 6:36 ` [gentoo-dev] " Duncan
2012-12-21 7:25 ` Ulrich Mueller
2012-12-20 18:14 ` [gentoo-dev] " Ciaran McCreesh
2012-12-20 20:50 ` Rick "Zero_Chaos" Farina
2012-12-22 17:33 ` Luca Barbato
2012-12-24 2:17 ` Sebastian Pipping
2012-12-24 9:08 ` Ulrich Mueller
2012-12-24 12:33 ` Michael Mol
2012-12-24 12:33 ` Diego Elio Pettenò
2012-12-24 13:32 ` Ulrich Mueller
2012-12-24 14:00 ` Diego Elio Pettenò
2012-12-24 15:43 ` Ulrich Mueller
2012-12-24 16:15 ` Diego Elio Pettenò
2012-12-25 11:02 ` Ulrich Mueller
2012-12-24 16:09 ` Rick "Zero_Chaos" Farina
2012-12-25 9:09 ` Michael Hampicke
2012-12-25 9:51 ` [gentoo-dev] " Duncan
2012-12-25 11:38 ` [gentoo-dev] " Peter Stuge
2012-12-24 14:10 ` Michael Mol
2012-12-24 13:06 ` Michał Górny
2012-12-24 16:08 ` Rick "Zero_Chaos" Farina
2012-12-24 9:11 ` Ciaran McCreesh
2012-12-24 14:47 ` vivo75 [this message]
2012-12-24 2:20 ` Sebastian Pipping
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50D86AF4.6020005@gmail.com \
--to=vivo75@gmail.com \
--cc=ciaran.mccreesh@googlemail.com \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox