From: Dmitry Makovey <mldimon@makovey.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] KDE4 + python3.1 == no system-config-printer-kde ?
Date: Tue, 14 Jun 2011 18:09:28 -0600 [thread overview]
Message-ID: <4DF7F838.7040205@makovey.net> (raw)
In-Reply-To: <201106140710.07576.michaelkintzios@gmail.com>
On 06/14/2011 12:09 AM, Mick wrote:
> The last enews I read specifically warned *not* to turn on 3.1 and
> instead
> stay with the latest 2 version ...
>
> Do you have a specific reason that compels you to try to make KDE work with
> 3.1?
If memory serves me right it was on this list that I picked up the idea
that things are working just fine with 3.1, not to mention that most
packages are "smart enough" to know which python they need with
PYTHON_API variables sprinkled around ebuilds. So I was quite surprised
to uncover this one.
next prev parent reply other threads:[~2011-06-15 0:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-14 5:43 [gentoo-user] KDE4 + python3.1 == no system-config-printer-kde ? Dmitry S. Makovey
2011-06-14 6:09 ` Mick
2011-06-15 0:09 ` Dmitry Makovey [this message]
2011-06-15 5:21 ` [gentoo-user] KDE4 + python3.1 == no system-config-printer-kde? Mick
-- strict thread matches above, loose matches on Subject: below --
2011-06-14 17:38 [gentoo-user] KDE4 + python3.1 == no system-config-printer-kde ? Ulrich Drolshagen
2011-06-15 23:59 ` Walter Dnes
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=4DF7F838.7040205@makovey.net \
--to=mldimon@makovey.net \
--cc=gentoo-user@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