All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Daniel Stone <daniel@fooishbar.org>
Cc: intel-gfx@lists.freedesktop.org, xorg-devel@lists.x.org,
	Julien Cristau <jcristau@debian.org>
Subject: Re: xf86-video-intel: configure.ac
Date: Tue, 27 Jul 2010 09:08:10 -0700	[thread overview]
Message-ID: <20100727090810.16a6ff32@virtuousgeek.org> (raw)
In-Reply-To: <20100727160028.GF2802@fooishbar.org>

On Tue, 27 Jul 2010 17:00:28 +0100
Daniel Stone <daniel@fooishbar.org> wrote:

> Hi,
> 
> On Tue, Jul 27, 2010 at 05:44:39PM +0200, Julien Cristau wrote:
> > On Tue, Jul 27, 2010 at 08:25:13 -0700, Jesse Barnes wrote:
> > > Apparently MeeGo does automatic packaging based on configure.ac, so
> > > Arjan requested that these be added to make that easier.
> > 
> > So we're adding fictional dependencies based on meego brokenness?
> > Do you have more details on the issues they were having?
> 
> That's pretty awesome.  In either case, xi is almost certainly the wrong
> module.  If the requirement is to have X11/extensions/XI.h and friends
> for server headers, then not only should that dep be in the server
> rather than a driver which blatantly has nothing to do with input, but
> you want inputproto rather than xi, which is libXi.

Agreed, since Arjan requested this I just pinged him about why he
thinks xi belongs here.  We don't directly include files from either
package, so putting the requirement on the server side makes more sense.

And I think the dep on glproto should be sufficient for the GL stuff we
use...

-- 
Jesse Barnes, Intel Open Source Technology Center

  reply	other threads:[~2010-07-27 16:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20100726234447.62A4410057@kemper.freedesktop.org>
     [not found] ` <20100726234447.62A4410057-PlYeExAEIo6UevrW7tnuMEsOKLKoXr+P@public.gmane.org>
2010-07-27 13:41   ` xf86-video-intel: configure.ac Julien Cristau
     [not found]     ` <20100727134135.GE10843-EvlgUWGjKCFw609as50hi2D2FQJk+8+b@public.gmane.org>
2010-07-27 14:50       ` Gaetan Nadon
2010-07-27 15:26         ` Jesse Barnes
2010-07-27 15:25     ` Jesse Barnes
2010-07-27 15:44       ` Julien Cristau
     [not found]         ` <20100727154439.GM12476-mjqoj5/V/3ubw+ijaxtQjQPnKcHpoCaU@public.gmane.org>
2010-07-27 16:00           ` [Intel-gfx] " Daniel Stone
2010-07-27 16:08             ` Jesse Barnes [this message]
2010-07-27 16:34             ` Jesse Barnes
     [not found]               ` <20100727093401.28506701-Y1mF5jBUw70BENJcbMCuUQ@public.gmane.org>
2010-07-27 16:39                 ` [Intel-gfx] " Daniel Stone
     [not found]                   ` <20100727163911.GI2802-rLtY4a/8tF1rovVCs/uTlw@public.gmane.org>
2010-07-27 16:47                     ` Julien Cristau
     [not found]                       ` <20100727164751.GA3096-mjqoj5/V/3ubw+ijaxtQjQPnKcHpoCaU@public.gmane.org>
2010-07-27 18:21                         ` Gaetan Nadon
2010-07-27 16:47                   ` Jesse Barnes
2010-07-28  8:42               ` Chris Wilson
2010-07-28 12:15                 ` Kristian Høgsberg
     [not found] <20101221223701.4B91F10057@kemper.freedesktop.org>
2010-12-21 22:56 ` Carl Worth

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=20100727090810.16a6ff32@virtuousgeek.org \
    --to=jbarnes@virtuousgeek.org \
    --cc=daniel@fooishbar.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jcristau@debian.org \
    --cc=xorg-devel@lists.x.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.