From: gevisz <gevisz@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Recommended location of the Gentoo ebuild repository
Date: Wed, 16 Dec 2020 17:44:00 +0200 [thread overview]
Message-ID: <CA+t6X7fQWVk+3XS_YmnevP3n2qnQ-Zspb5jkZcd2Z4oPgOp9=g@mail.gmail.com> (raw)
In-Reply-To: <CAGfcS_mCGS-2gQs8y54PwB6ZXwL64Zw-14Gbupv48mCCqAm0GQ@mail.gmail.com>
ср, 16 дек. 2020 г. в 16:55, Rich Freeman <rich0@gentoo.org>:
>
> On Wed, Dec 16, 2020 at 9:45 AM gevisz <gevisz@gmail.com> wrote:
> >
> > Nevertheless, the explanation why /var/db/repos/gentoo is better than
> > /usr/portage is still welcomed. :)
> >
>
> There is a lengthy discussion on gentoo-dev on this, and my personal
> first choice didn't win. :)
>
> There is little dispute that /var makes more sense than /usr other
> than legacy reasons. /usr is generally used for static data - on some
> distros it might even be read-only, a squashfs, signed using crypto,
> and so on. On a rolling release distro like Gentoo it might get
> changed often by updates, but other than system updates nothing in it
> should change. On a more release-based distro only security updates
> or major releases would touch it.
>
> /var on the other hand is used for application data and other things
> that change all the time. That includes things like databases, which
> the Gentoo repo basically is. Mail spools, print spools, caches, and
> so on all go on there.
>
> FHS formalizes all this stuff.
>
> Now, where exactly in /var it goes is more a matter of debate.
> /var/db is not specified in FHS, but it is used by FreeBSD which I
> think was one of the selling points. Personally I stick it in
> /var/cache as (IMO) it just contains a local copy of a repository that
> is entirely stored elsewhere. Some would certainly disagree with
> that. I think /var/lib would be an alternative place that keeps more
> to FHS.
>
> However, moving it out of /usr was a move with near-universal support.
> And you can really put it anywhere you want by editing one line in
> your portage config. I don't think the directory even exists in the
> base install - it gets created the first time you sync so it is
> entirely user-configurable.
Ok, thank you for the explanation.
next prev parent reply other threads:[~2020-12-16 15:44 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 [this message]
2020-12-16 14:58 ` Mark Knecht
2020-12-16 15:25 ` antlists
2020-12-16 15:34 ` Rich Freeman
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='CA+t6X7fQWVk+3XS_YmnevP3n2qnQ-Zspb5jkZcd2Z4oPgOp9=g@mail.gmail.com' \
--to=gevisz@gmail.com \
--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