From: Mike Kazantsev <mk.fraggod@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] layman tree (re)location - /usr/local
Date: Tue, 2 Jun 2009 21:19:30 +0600 [thread overview]
Message-ID: <20090602211930.44bbbdf7@coercion> (raw)
[-- Attachment #1: Type: text/plain, Size: 805 bytes --]
Answer in a neighbor thread reminded me of a question that puzzled me
from the start: what's the rationale behind moving layman tree
from /usr/portage/local to /usr/local/portage?
I can see why all ebuilds belong in the same /usr/portage tree -
separate (optimized) fs, easy to backup (snapshot?) or omit from backup
(a lot of small files, completely irrelevant to system operation), easy
to share between several machines along w/ packages built from it,
and /usr/portage/packages should be inconsistent w/o layman tree, if
it's used at all... but moving it to /usr/local, which isn't used
by gentoo at all seem completely irrational to me, why?
Oh, and I know that I can keep it all in the same place, of course, and
I always do just that, still...
--
Mike Kazantsev // fraggod.net
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2009-06-02 15:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-02 15:19 Mike Kazantsev [this message]
2009-06-02 19:01 ` [gentoo-user] layman tree (re)location - /usr/local Sebastian Günther
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=20090602211930.44bbbdf7@coercion \
--to=mk.fraggod@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