From: Armando Di Cianno <fafhrd@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] any interest in removing /usr/qt and /usr/kde ?
Date: Mon, 20 Sep 2004 11:56:29 -0400 [thread overview]
Message-ID: <8149d45f8542724f660586f0d314123d@mudra> (raw)
In-Reply-To: <200409201147.18918@malte.stretz.eu.org>
On 2004-09-20 05:47:18 -0400 Malte S. Stretz
<msquadrat.nospamplease@gmx.net> wrote:
> I don't propose to create something completely new like, say, what
> Apple uses
> in MacOS X, just to refine the current state of art. As I said, it's
> not
> like we lack space in / or need to look like a "real" SysV system.
> Linux (or
> GNU/Linux if you prefer that) is IMO about invention, so why do we
> try to
> cram everything into the olde Unix directory structure while it
> obviously
> doesn't fit?
Just to be ontologically aligned with those that created the NeXTStep
hierarchy, OS X (NeXTStep/OpenStep's logical descendants [alongside
GNUstep]) has it's own UNIX-y/FHS-y hierarchy, from the BSD tools,
_and_ a NeXT-y hierarchy.
I chimed in before about what I should do with GNUstep, but whereever
in the UNIX-y hierarchy it lives, it's packages are going to be
installed underneath it, e.g /opt/GNUstep, /usr/GNUstep, etc.
Classically, on UNIX-y systems ('cause it can run on Windows, too) the
preferred spot is /usr/GNUstep. This was likely chosen by the
original authors thinking "Hey, that's what X11 did...".
This is a concern for me, not because GNUstep is "big" and will cause
"pollution," but because it is _different_ than what the FHS was
designed for.
__armando
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-09-20 15:53 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-19 19:50 [gentoo-dev] any interest in removing /usr/qt and /usr/kde ? Thomas Weidner
2004-09-19 19:52 ` Ciaran McCreesh
2004-09-19 20:07 ` Mike Frysinger
2004-09-19 20:06 ` Dan Armak
2004-09-19 20:07 ` Joshua J. Berry
2004-09-19 20:13 ` Ciaran McCreesh
2004-09-19 20:16 ` Dan Armak
2004-09-19 20:26 ` Joshua J. Berry
2004-09-19 20:29 ` Ciaran McCreesh
2004-09-19 22:23 ` Joshua J. Berry
2004-09-20 8:41 ` Paul de Vrieze
2004-09-19 20:37 ` Dan Armak
2004-09-19 21:23 ` Malte S. Stretz
2004-09-19 23:38 ` Armando Di Cianno
2004-09-20 8:48 ` Paul de Vrieze
2004-09-20 9:47 ` Malte S. Stretz
2004-09-20 15:56 ` Armando Di Cianno [this message]
2004-09-20 19:52 ` Malte S. Stretz
2004-09-20 15:40 ` Dan Armak
2004-09-20 18:30 ` Paul de Vrieze
2004-09-20 19:45 ` Malte S. Stretz
2004-09-19 22:35 ` Joshua J. Berry
2004-09-20 4:10 ` Dan Armak
2004-09-20 4:27 ` Mike Frysinger
2004-09-20 4:47 ` Luke-Jr
2004-09-20 6:09 ` Joshua J. Berry
2004-09-20 9:05 ` Paul de Vrieze
2004-09-20 15:55 ` Sami Samhuri
2004-09-20 16:22 ` Carsten Lohrke
2004-09-20 16:36 ` Malte S. Stretz
2004-09-20 16:44 ` Dan Armak
2004-09-20 17:19 ` Malte S. Stretz
2004-09-20 17:36 ` Dan Armak
2004-09-20 22:58 ` foser
2004-09-20 17:42 ` Carsten Lohrke
2004-09-20 16:37 ` Dan Armak
2004-09-20 17:35 ` Carsten Lohrke
2004-09-20 18:52 ` Paul de Vrieze
2004-09-20 19:17 ` Carsten Lohrke
2004-09-21 10:47 ` [gentoo-dev] " Duncan
2004-09-21 11:02 ` Duncan
2004-09-21 12:05 ` Carsten Lohrke
2004-09-21 4:58 ` Joel Konkle-Parker
2004-09-21 9:49 ` Paul de Vrieze
2004-09-20 7:49 ` [gentoo-dev] " Simon Watson
2004-09-19 20:09 ` Paul de Vrieze
2004-09-28 2:51 ` [gentoo-dev] " John Croisant
2004-09-28 8:19 ` Paul de Vrieze
2004-09-28 9:24 ` Peter Ruskin
2004-09-28 9:37 ` Paul de Vrieze
2004-09-28 20:32 ` John Croisant
2004-09-29 9:07 ` Paul de Vrieze
2004-09-19 21:55 ` [gentoo-dev] " Luke-Jr
2004-09-19 23:06 ` [gentoo-dev] " Thomas Weidner
2004-09-20 0:03 ` Luke-Jr
2004-09-20 0:55 ` Ciaran McCreesh
2004-09-20 3:50 ` Luke-Jr
2004-09-21 5:10 ` Joel Konkle-Parker
2004-09-21 17:29 ` Helmar Wieland
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=8149d45f8542724f660586f0d314123d@mudra \
--to=fafhrd@gentoo.org \
--cc=gentoo-dev@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