From: Paul de Vrieze <pauldv@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] problems with need-kde/qt and possible solutions
Date: Fri, 6 Aug 2004 12:52:29 +0200 [thread overview]
Message-ID: <200408061252.29350.pauldv@gentoo.org> (raw)
In-Reply-To: <200407310222.28132.carlo@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 676 bytes --]
On Saturday 31 July 2004 02:22, Carsten Lohrke wrote:
> I played with the kde.eclass today, to be sure what can/has to be done, to
> remove the problematic need-kde/qt functions from ebuilds. For reasons see
> Bug 25013 (comment 50 ff.) and Bug 58819.
>
What about having different eclasses for the different versions? If those
eclasses inherit a common one, this would probably be the cleanest solution.
To introduce a set_dependencies() function would only have the problem appear
somewhere else. It still would break the cache and/or partial parsing
Paul
--
Paul de Vrieze
Gentoo Developer
Mail: pauldv@gentoo.org
Homepage: http://www.devrieze.net
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-08-06 10:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-31 0:22 [gentoo-dev] problems with need-kde/qt and possible solutions Carsten Lohrke
2004-08-06 10:52 ` Paul de Vrieze [this message]
2004-08-10 23:34 ` Carsten Lohrke
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=200408061252.29350.pauldv@gentoo.org \
--to=pauldv@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