From: Donnie Berkholz <dberkholz@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] virtualx eclass
Date: Thu, 16 Oct 2008 14:54:32 -0700 [thread overview]
Message-ID: <20081016215432.GA15437@comet> (raw)
In-Reply-To: <48F75F30.7030408@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 2058 bytes --]
On 11:35 Thu 16 Oct , Doug Goldstein wrote:
> Doug Goldstein wrote:
> > While the rule of thumb has been if an eclass needs something it should
> > provide it's own depends. However the virtualx eclass needs to be
> > different simply because in some cases it's only uses for tests (this is
> > it's most common usage in the whole) tree. When it's used for tests
> > pulling in the xorg-server the most ideal situation would be if
> > xorg-server was only pulled in on USE=test because currently for anyone
> > emerging an app that uses GTK+ they have a weird situation in the fact
> > that all of GTK+'s depends that have USE=X use it to mean libX11 (as do
> > most usages of the X USE flag), however GTK+ itself due to it's usage of
> > the virtualx eclass pulls in xorg-server when USE=X, which is only used
> > for tests. This results in a confusing experience for users looking to
> > built a headless machine.
> >
> > It'd be a lot more consistent if ebuilds provided a USE flag or directly
> > depended on the xorg-server and then used the functions in the eclass.
> > So in summary, those are the changes I plan on making very shortly. If
> > someone's got some input, please speak up.
> >
> >
> Alright... after talking to Diego, Dave, and Remi the final result that
> I've come up with is the following:
>
> VIRTUALX_CONDITIONAL_USE="test"
>
> inherit virtualx
>
> That'll result in virtualx adding the following:
>
> DEPEND="test? ( x11-base/xorg-server x11-apps/xhost )"
>
> if VIRTUALX_CONDITIONAL_USE is unset (as it will be for all ebuilds
> initially) the default will be "X". Which means the default is the same
> as what we've got today. If it's set to an empty string, it'll always be
> required. Otherwise, it will use the supplied USE flag.
I'm not sure whether this would work, but one idea would be to handle
dependencies depending on what's in IUSE of the ebuild inheriting.
--
Thanks,
Donnie
Donnie Berkholz
Developer, Gentoo Linux
Blog: http://dberkholz.wordpress.com
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-10-16 21:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-16 13:44 [gentoo-dev] virtualx eclass Doug Goldstein
2008-10-16 14:17 ` [gentoo-dev] " Diego 'Flameeyes' Pettenò
2008-10-16 14:32 ` Doug Goldstein
2008-10-16 15:15 ` Doug Goldstein
2008-10-16 14:18 ` [gentoo-dev] " Doug Goldstein
2008-10-16 15:35 ` Doug Goldstein
2008-10-16 21:54 ` Donnie Berkholz [this message]
2008-10-16 23:18 ` Bo Ørsted Andresen
2008-10-20 21:50 ` Doug Goldstein
2008-10-22 11:06 ` Petteri Räty
2008-10-28 17:32 ` Doug Goldstein
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=20081016215432.GA15437@comet \
--to=dberkholz@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