From: Chris Moore <kurisu@softhome.net>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] FHS compliance
Date: Sat, 02 Feb 2002 00:42:32 -0800 [thread overview]
Message-ID: <3C5BA678.5050802@softhome.net> (raw)
I don't know if this is the right place to post this but whatever...
Gentoo is an awesome distrobution and about the only thing that I can
point my finger on that I would like to see changed is FHS compliance
(well mostly...) For the most part it even meets fhs compliance but
here is (and I know this would take some work...) how to fix it.
Move the portage package ebuild filetree from /usr/portage to
/var/lib/portage ( See 5.8.3 +-<pkgtool> and cross reference the
purposes of the /usr hierarchy with the purpose of /var which is
summarized as follows: /usr's purpose is shareable read-only data
(ebuilds are updated!) /var's purpose is sharable/unsharable DYNAMIC
application data (such as the ebuild dirtree) and /var/lib has the
specific option for the package tool's dynamic data)
Why would anyone want to do this you ask. Well, standards are only as
good as we make them by embracing them... One complaint about *nix is
that the filesystem is difficult to navigate leaving you guessing as to
where you need to look for something as it can change from computer to
computer. This standard tries to remove that confusion.
Regardless I understand it is a lot of work to move around etc. but I
think that it is a good move that makes more sense.
--
Chris Moore
---------------------------------
Born Again Bourne Again Believer:
New Life, GNU/Linux
Be Free
next reply other threads:[~2002-02-02 8:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-02 8:42 Chris Moore [this message]
2002-02-02 19:32 ` [gentoo-dev] FHS compliance Chad M. Huneycutt
2002-02-07 16:09 ` Chris Houser
2002-02-07 16:32 ` John Stalker
2002-02-07 21:40 ` George Shapovalov
2002-02-07 22:50 ` Sebastian Werner
2002-02-08 16:07 ` gentoo-user
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=3C5BA678.5050802@softhome.net \
--to=kurisu@softhome.net \
--cc=gentoo-dev@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