public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Spider <spider@gentoo.org>
To: Collins <erichey2@attbi.com>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] gentoo & fhs
Date: Tue, 2 Jul 2002 02:50:57 +0200	[thread overview]
Message-ID: <20020702025057.0cada85f.spider@gentoo.org> (raw)
In-Reply-To: <20020701173735.5d1093ae.erichey2@attbi.com>

[-- Attachment #1: Type: text/plain, Size: 1307 bytes --]

I think this is the best explination of it :

http://www.pathname.com/fhs/2.2/fhs-3.12.html

since we dont "add on" either KDE or Gnome I say... Give the man a
balloon.


compare with this though:
<quote>
Large software packages must not use a direct subdirectory under the
/usr hierarchy. 
</quote>
http://www.pathname.com/fhs/2.2/fhs-4.1.html


//Spider


begin  quote
On Mon, 1 Jul 2002 17:37:35 -0600
Collins <erichey2@attbi.com> wrote:

> Just finished a lengthy interchange wih a "gentleman" (loosely
> speaking) on another group this weekend.  Said gentleman considers
> himself to be a chief priest of the fhs religion, and he says that he
> wouldn't touch gentoo with a fork because gnome and kde are in the
> /usr hierarchy instead of the /opt hierarchy "where god intended them
> to be."
> 
> Just curious, is he all wet, or is this a conscious departure from the
> fhs requirements?
> 
> -- 
> Collins Richey - Denver Area - WWTLRD?
> gentoo(since 01/01/01) 2.4.18+(ext3) xfce-sylpheed-mozilla
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev


--
begin  .signature
This is a .signature virus! Please copy me into your .signature!
See Microsoft KB Article Q265230 for more information.
end

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2002-07-02  0:54 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-01 23:37 [gentoo-dev] gentoo & fhs Collins
2002-07-01 16:06 ` Miguel S. Filipe
2002-07-02  0:50 ` Spider [this message]
     [not found]   ` <20020701190627.28c32c2e.erichey2@attbi.com>
2002-07-02  1:47     ` Spider
2002-07-02  2:38       ` Collins
2002-07-02 12:02         ` Alexander Gretencord
2002-07-02 15:12           ` Karl Trygve Kalleberg
2002-07-02 12:53         ` [gentoo-user] " Grant Goodyear
2001-12-08 13:21           ` Maciek Borowka
2002-07-02 15:55           ` Jean-Michel Smith
2002-07-02 17:00           ` Bart Verwilst
2002-07-02 18:41         ` [gentoo-dev] Why the FHS can't be followed Dan Armak
2002-07-02 19:10           ` Jean-Michel Smith
2002-07-02 20:06             ` Luke Ravitch
2002-07-02 22:00               ` Jean-Michel Smith
2002-07-03  1:54                 ` Luke Ravitch
2002-07-03  3:08                   ` Fuper
2002-07-05 16:33                     ` [gentoo-dev] Stow (Was: Why the FHS can't be followed) Wout Mertens
2002-07-05 16:59                       ` Brian Webb
2002-07-05 22:39                         ` Fuper
2002-07-05 17:14                       ` Alexander Gretencord
2002-07-02 22:18               ` [gentoo-dev] Why the FHS can't be followed Fuper
2002-07-03  2:05                 ` Luke Ravitch
2002-07-03  1:10               ` Peter Ruskin
2002-07-02 20:55           ` Terje Kvernes
2002-07-02 15:09 ` [gentoo-dev] gentoo & fhs Karl Trygve Kalleberg

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=20020702025057.0cada85f.spider@gentoo.org \
    --to=spider@gentoo.org \
    --cc=erichey2@attbi.com \
    --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