public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Albert Hopkins <marduk@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Symlinking /usr/portage/distfiles
Date: Tue, 30 Jan 2007 06:59:22 -0600	[thread overview]
Message-ID: <1170161962.27808.10.camel@blackwidow.nbk> (raw)
In-Reply-To: <200701292112.22080.alan@linuxholdings.co.za>

I think you confused my message.  When I said "I've always been told..."
I didn't mean I was told it was part of the standard, I mean it is
common knowledge, common sense, rule-of-thumb, best practice --
whatever. Yes there is FHS but I don't consider it the Bible.  most
distros break FHS in some way anyhow... I mean let's get a little
realistic here.  We're talking about temporary files, not /etc/passwd...

My main point was not to point out theory (FHS) but practice.  Over two
years of use shows that it is perfectly fine to run portage in /tmp
(with tmp on tmpfs) and, if you take a second to think about it, it does
make sense that that would be a viable alternative.  You mentioned
exceptions like OpenOffice and I suggested a workaround.  As always
YMMV.


-- 
gentoo-user@gentoo.org mailing list



  parent reply	other threads:[~2007-01-30 13:04 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-27 13:16 [gentoo-user] Symlinking /usr/portage/distfiles Vlad Dogaru
2007-01-27 13:29 ` Mick
2007-01-27 13:31 ` Dale
2007-01-27 16:40   ` Vlad Dogaru
2007-01-27 18:14     ` Jürgen Geuter
2007-01-27 19:05       ` Jeffrey Rollin
2007-01-27 19:52         ` Vlad Dogaru
2007-01-27 23:48         ` Neil Bothwick
2007-01-29  7:38     ` Alan McKinnon
2007-01-29 13:20       ` Albert Hopkins
     [not found]         ` <200701292112.22080.alan@linuxholdings.co.za>
2007-01-30  9:29           ` Neil Bothwick
2007-01-30 12:22           ` Bo Ørsted Andresen
2007-01-30 13:09             ` Neil Bothwick
2007-01-30 12:59           ` Albert Hopkins [this message]
2007-01-30  7:25       ` Bo Ørsted Andresen
     [not found] ` <200701301422.12957.bo.andresen@zlin.dk>
     [not found]   ` <200701301552.37737.alan@linuxholdings.co.za>
2007-01-30 14:06     ` Uwe Thiem
2007-01-31 11:02       ` Alan McKinnon
2007-01-31 12:22         ` Uwe Thiem
2007-01-31 12:34           ` Bo Ørsted Andresen
2007-01-31 13:23             ` Alan McKinnon
2007-01-31 13:22           ` Alan McKinnon
2007-01-31 13:38           ` Bo Ørsted Andresen
2007-01-31 15:58             ` Alan McKinnon
2007-01-31 19:13               ` Boyd Stephen Smith Jr.
2007-01-31 23:49                 ` Mark Kirkwood
2007-02-01  8:51                   ` Nelson, David (ED, PAR&D)
2007-02-01  9:10                     ` Alan McKinnon
2007-02-01 18:43           ` Ralf Stephan
2007-02-01 20:41             ` Dan Farrell
2007-01-30 14:35   ` Neil Bothwick
2007-01-30 16:26     ` Anthony E. Caudel
2007-01-31 11:16       ` Alan McKinnon
2007-01-31 12:25         ` Dan Farrell
2007-02-01 10:30           ` Neil Bothwick
2007-01-31 15:22         ` Anthony E. Caudel
2007-01-30 19:10     ` Mick
2007-01-30 19:31       ` Neil Bothwick
2007-01-30 20:18       ` Albert Hopkins
2007-01-30 22:39         ` Neil Bothwick
2007-01-31  0:45           ` Steve Dibb
2007-01-31  1:22             ` Neil Bothwick
2007-01-31 10:37               ` Boyd Stephen Smith Jr.

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=1170161962.27808.10.camel@blackwidow.nbk \
    --to=marduk@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