public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Pending layman directory "relocation"
Date: Wed, 3 Mar 2010 18:42:33 +0200	[thread overview]
Message-ID: <201003031842.33792.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <201003031733.54131.wonko@wonkology.org>

On Wednesday 03 March 2010 18:33:52 Alex Schuster wrote:
> Alan McKinnon writes:
> > On Wednesday 03 March 2010 14:21:23 Neil Bothwick wrote:
> > > That's right, they should both be in /var.
> > 
> > I concur. /usr has a long tradition is Unix of often being mounted
> > read-only (think thin clients that mount it over NFS).
> 
> Any idea why it's different with Gentoo in the first place? /usr also
> always sounded wrong to me for the portage tree.
> And for other things. Shouldn't /usr/src go somewhere into /var? And
> shouldn't /usr/share/config stuff be in /etc?

/usr/src/ is the traditional place for kernel header files. They are intended 
to be static, change seldom, and definitely not something that users can 
change. Normally, root would update them when needed, and stuff can then build 
against them.

/usr/share/config/ is an upstream thing and if you follow FHS then /etc/ is a 
better place. But Gentoo follows upstream as much as possible so this one gets 
left as-is.

NB: Gentoo only follows FHS when it suits Gentoo devs to do it :-) The 
reasoning offered is usually that Gentoo is a source distro and therefore has 
little needs of FHS, which does tend towards compatibility between binary 
distros

> 
> > My set up is:
> > 
> > portage:	/var/portage/
> > my overlay:	/var/portage/local/alan/
> > layman:		/var/portage/local/layman/*
> > 
> > As portage is hard-coded to not fiddle with $PORTDIR/local/, this works
> > well for me and every ebuild on the system is under one mount point.
> 
> Where do you have the distfiles? I now have it like this:

/var/distfiles/
/var/packages/
/var/rpm/

I do it this way as I am confident portage will leave /var/portage/local/ 
alone, I have no confidence it will do the same for the above three. Plus, 
those dirs can get big, and I keep the portage volume small and tight for 
performance reasons

-- 
alan dot mckinnon at gmail dot com



  reply	other threads:[~2010-03-03 16:45 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-01 18:08 [gentoo-user] Pending layman directory "relocation" 7v5w7go9ub0o
2010-03-01 18:26 ` [gentoo-user] " Nikos Chantziaras
2010-03-01 19:07   ` 7v5w7go9ub0o
2010-03-01 23:09     ` Neil Bothwick
2010-03-02 16:56       ` 7v5w7go9ub0o
2010-03-02 18:07         ` Zeerak Mustafa Waseem
2010-03-01 20:19   ` Tanstaafl
2010-03-01 21:05     ` Alan McKinnon
2010-03-01 18:30 ` [gentoo-user] " Tanstaafl
2010-03-01 19:02   ` [gentoo-user] " 7v5w7go9ub0o
2010-03-01 20:10     ` Tanstaafl
2010-03-01 19:14   ` [gentoo-user] " Alan McKinnon
2010-03-02 15:51   ` Peter Humphrey
2010-03-03 11:10     ` Stroller
2010-03-03 12:21       ` Neil Bothwick
2010-03-03 12:49         ` Alan McKinnon
2010-03-03 16:33           ` Alex Schuster
2010-03-03 16:42             ` Alan McKinnon [this message]
2010-03-03 16:43             ` stosss
2010-03-03 16:45               ` Alan McKinnon
2010-03-03 17:03             ` Stroller

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=201003031842.33792.alan.mckinnon@gmail.com \
    --to=alan.mckinnon@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