From: William Kenworthy <billk@iinet.net.au>
To: Luke-Jr <luke-jr@gentoo.org>
Cc: gentoo-dev List <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] gentoo vs. the FHS
Date: 24 Sep 2003 08:21:14 +0800 [thread overview]
Message-ID: <1064362874.10322.90.camel@rattus.localdomain> (raw)
In-Reply-To: <200309232312.05766.luke-jr@gentoo.org>
As someone who works with a number of different OS's daily, from solaris
to various flavours of linux - the FHS and standards compliance is a
godsend. The FHS has a few warts, and slavish compliance with it is not
desired, but generally, it is a "good thing". Just because commercial
apps use it, doesnt mean its bad for everyone else, they just benefit
too.
BillK
On Wed, 2003-09-24 at 07:11, Luke-Jr wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Tuesday 23 September 2003 10:12 pm, dams@idm.fr wrote:
> > FHS is made so that f*cking proprietary application get well installed on
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-09-24 0:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-22 6:32 [gentoo-dev] gentoo vs. the FHS aeriksson
2003-09-23 20:08 ` Stanislav Brabec
2003-09-23 20:26 ` Matt Chorman
2003-09-23 20:58 ` Caleb Tennis
2003-09-23 22:12 ` dams
2003-09-23 23:11 ` Luke-Jr
2003-09-24 0:21 ` William Kenworthy [this message]
2003-09-24 3:33 ` Daniel Robbins
2003-09-24 7:18 ` Sven Vermeulen
2003-09-24 1:08 ` Kevin Lacquement
2003-09-24 7:20 ` Sven Vermeulen
2003-09-24 3:32 ` Daniel Robbins
2003-09-23 21:26 ` Paul de Vrieze
2003-09-24 14:21 ` splite-gentoo
2003-09-24 18:10 ` Stanislav Brabec
2003-09-24 2:37 ` Mike Frysinger
2003-09-24 3:35 ` Daniel Robbins
2003-09-29 3:47 ` Mike Frysinger
2003-09-29 15:18 ` Luke-Jr
2003-09-30 12:59 ` Stuart Herbert
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=1064362874.10322.90.camel@rattus.localdomain \
--to=billk@iinet.net.au \
--cc=gentoo-dev@gentoo.org \
--cc=luke-jr@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