public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dan Armak <danarmak@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 20:36:53 +0300	[thread overview]
Message-ID: <200409202036.53693.danarmak@gentoo.org> (raw)
In-Reply-To: <200409201919.23392@malte.stretz.eu.org>

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

On Monday 20 September 2004 20:19, Malte S. Stretz wrote:
> Yes.  The reason is that this would make KDE follow the rationale behind
> the FHS most:  Stuff in share can generally be shared (eg. NFS-mounted)
> across several machines, while lib continas platform-specific stuff and
> bin... you get the point.  This might happen rarely but it's the intention
> behind the split done in the FHS.
I see.

>
> I don't know what you mean with docs which don't belong below lib in your
> other mail, was it a misunderstanding of Carsten's mail?
My point was that since lib is meant for, well, libraries (and occasional 
binaries), it'd be inappropriate to put things like docs under it. Just 
inelegant, and people wouldn't expect it. Especially in view of the 
filesystem sharing scenario you outlined.

>
> > Specifying such separate dirs rather than a unified KDEDIR/KDEDIRS looks,
> > at first sight, to be a major PITA. Maybe they'll improve support for
> > this in kde4, but I don't relish the thought of doing it with 3.x. Unless
> > there's a way already to specify such separated dirs via env variables a
> > la KDEDIRS that I'm not aware of?
>
> I didn't say that this is already possible without much headache, just that
> it's maybe the best/cleanest solution for some distant future.
Definitely - if KDE makes it as easy as KDEDIRS, I'd vote for such a solution 
too in the longterm.

>
> But actually, even currently I don't see a problem with that; the configure
> line would become rather long ('./configure --bindir=/usr/bin/kde/3.3
> --datadir=/usr/share/kde/3.3 ...') but at least there it would work.  And
> those dirs are available via eg. 'kde-config --path data' later on.
>
> But I don't know how many stuff inside KDE or how many third-party tools
> depend on a "flat" $KDEDIR available via the environment variable(s) so
> this might indeed be stuff for KDE 4.
Seems like it to me, too.

>
> OTOH is it not like the current approach with /usr/kde eats your children
> or burns your box.  It's just not nice and FHS compliant and stuff but has
> been there for quite some time now and could stay as it is for another year
> or so until KDE 4 is released.  IMHO.
Agreed.

> Btw, all this discussion was about KDE, I wonder how GNOME handles this
> stuff.  Does it also use /usr/gnome/x.y or so something else?
No idea. I seem to remember gnome 1.4 and 2.0 coexisted back in the day, but 
don't remember how... Any gnome devs reading this thread? ;-)

-- 
Dan Armak
Gentoo Linux developer (KDE)
Matan, Israel
Public GPG key: http://dev.gentoo.org/~danarmak/danarmak-gpg-public.key
Fingerprint: DD70 DBF9 E3D4 6CB9 2FDD  0069 508D 9143 8D5F 8951

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

  reply	other threads:[~2004-09-20 17:35 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
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 [this message]
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=200409202036.53693.danarmak@gentoo.org \
    --to=danarmak@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