From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Re: KDE 3.4 visibility support disabled
Date: Thu, 26 May 2005 16:23:31 -0700 [thread overview]
Message-ID: <pan.2005.05.26.23.23.29.991357@cox.net> (raw)
In-Reply-To: 200505261205.40902.cryos@gentoo.org
Marcus D. Hanwell posted <200505261205.40902.cryos@gentoo.org>, excerpted
below, on Thu, 26 May 2005 12:05:36 +0100:
> It seems that this has already been answered, but the KDE bug contains
> some more of the detail. It looks like KDE 3.5/4 is the target for getting
> proper visibility support. We haven't taken this decision lightly, and I
> believe it is the best option we have for a stable desktop.
>
> KDE/QT 4 should have much improved visibility support, and I will be
> testing them once it is workable and I have a little spare time
Yes, I'm pretty much resigned to having to wait until kde4 for proper gcc4
support, but am /really/ looking forward to that!
BTW, it's a bit off topic for this thread, but if there's someplace you
could point me to with updated info on what's happening to arts and/or
what's going to be replacing it in kde4, I know quite a number of folks
that are interested. It seems I knew more than most when the topic came
up in at least two groups (the amd64 list, and the local *ix group here at
Cox), but my info is now severely outdated, since most of it is from last
year's aKademy coverage and the like, when the only thing really settled
was that 3.4 would continue to use ARTS and they would look at a
replacement for 4.0. Now that 4.0 is getting closer, one would hope the
kde4 sound question has been resolved rather more concretely than that,
and as I said, I know a lot of folks (certainly myself included) that will
be interested in learning more about whatever has been concluded.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman in
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html
--
gentoo-dev@gentoo.org mailing list
prev parent reply other threads:[~2005-05-26 23:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-25 16:48 [gentoo-dev] KDE 3.4 visibility support disabled Marcus D. Hanwell
2005-05-25 18:02 ` Jason Wever
2005-05-25 23:37 ` [gentoo-dev] " Duncan
2005-05-25 23:57 ` Diego 'Flameeyes' Pettenò
2005-05-26 4:25 ` [gentoo-dev] Re: [gentoo-amd64] " Dan Armak
2005-05-26 7:30 ` [gentoo-dev] " Duncan
2005-05-26 12:26 ` Caleb Tennis
2005-05-26 16:09 ` Andreas Fredriksson
2005-05-26 11:05 ` [gentoo-dev] " Marcus D. Hanwell
2005-05-26 23:23 ` Duncan [this message]
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=pan.2005.05.26.23.23.29.991357@cox.net \
--to=1i5t5.duncan@cox.net \
--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