From: Peter Ruskin <Peter.Ruskin@dsl.pipex.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: any interest in removing /usr/qt and /usr/kde ?
Date: Tue, 28 Sep 2004 10:24:31 +0100 [thread overview]
Message-ID: <200409281024.31287.Peter.Ruskin@dsl.pipex.com> (raw)
In-Reply-To: <200409281019.35486.pauldv@gentoo.org>
On Tuesday 28 September 2004 09:19, Paul de Vrieze wrote:
> Do you realize that this would amount to serious patches on kde. KDE
> expects KDEDIR(S) to work the way it does currently. I know it is not
> ideal, but neither is the FHS.
Well I think it *is* ideal the way we have it - that was one of the many
things that attracted me to Gentoo in the first place. It's the most
sensible way I've come across for organizing KDE/Qt and we should not
even consider abandoning it.
--
Peter
========================================================================
Gentoo Linux: Portage 2.0.50-r11. kernel-2.6.8-gentoo-r4.
i686 AMD Athlon(tm) XP 3200+. gcc(GCC): 3.4.2.
KDE: 3.3.0. Qt: 3.3.3.
========================================================================
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-09-28 9:24 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
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 [this message]
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=200409281024.31287.Peter.Ruskin@dsl.pipex.com \
--to=peter.ruskin@dsl.pipex.com \
--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