From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Recommended location of the Gentoo ebuild repository
Date: Wed, 16 Dec 2020 10:34:25 -0500 [thread overview]
Message-ID: <CAGfcS_=7cfmF=99qOnHMp5Mw1bEiEBczUqWp+RFrKFe50tWLkw@mail.gmail.com> (raw)
In-Reply-To: <769a00cf-3759-016a-816d-d83443faa560@youngman.org.uk>
On Wed, Dec 16, 2020 at 10:25 AM antlists <antlists@youngman.org.uk> wrote:
>
> Here we are storing the data (source files) used to build a gentoo
> system. So while it may be a bit tenuous (I find Rich's argument for
> "cache" more compelling), I don't think the argument for calling this a
> database that strange - portage the system uses portage the data to
> build the system called gentoo ...
Oh, I would agree that Portage is a database, but if you want to go
with that then /var/lib is the correct location. /var/db is not where
you would store a database per FHS. In FHS /var/db doesn't exist at
all. :)
Really the main difference between /var/cache and /var/lib is
value/persistance. The point of a cache is that you can toss it at
any time and re-create it. That isn't true of the stuff in /var/lib.
Which bucket the package repo fits into is somewhat nuanced.
--
Rich
next prev parent reply other threads:[~2020-12-16 15:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 11:51 [gentoo-user] Recommended location of the Gentoo ebuild repository gevisz
2020-12-16 11:54 ` Miles Malone
2020-12-16 14:45 ` gevisz
2020-12-16 14:55 ` Rich Freeman
2020-12-16 15:30 ` Victor Ivanov
2020-12-16 15:44 ` gevisz
2020-12-16 14:58 ` Mark Knecht
2020-12-16 15:25 ` antlists
2020-12-16 15:34 ` Rich Freeman [this message]
2020-12-16 15:52 ` Mark Knecht
2020-12-16 15:14 ` [gentoo-user] " Nikos Chantziaras
2020-12-16 15:41 ` Dale
2020-12-20 17:08 ` Peter Humphrey
2020-12-20 17:16 ` Dale
2020-12-21 9:11 ` Peter Humphrey
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='CAGfcS_=7cfmF=99qOnHMp5Mw1bEiEBczUqWp+RFrKFe50tWLkw@mail.gmail.com' \
--to=rich0@gentoo.org \
--cc=gentoo-user@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