From: Ben Widawsky <ben@bwidawsk.net>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [IGT PATCH] README: list some of the dependencies
Date: Wed, 9 Oct 2013 07:46:26 -0700 [thread overview]
Message-ID: <20131009144625.GA13399@bwidawsk.net> (raw)
In-Reply-To: <87d2ne3opf.fsf@intel.com>
On Wed, Oct 09, 2013 at 10:09:32AM +0300, Jani Nikula wrote:
> On Wed, 09 Oct 2013, Ben Widawsky <ben@bwidawsk.net> wrote:
> > On Tue, Oct 08, 2013 at 09:19:06PM +0300, Jani Nikula wrote:
> >> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> >> ---
> >> README | 12 ++++++++++++
> >> 1 file changed, 12 insertions(+)
> >>
> >> diff --git a/README b/README
> >> index 653bfcd..a04c987 100644
> >> --- a/README
> >> +++ b/README
> >> @@ -96,3 +96,15 @@ debugger/
> >> initiating connections with debug clients..
> >>
> >> The debugger must be run as root: "sudo debugger/eudb"
> >> +
> >> +DEPENDENCIES
> >> + This is a non-exchaustive list of package dependencies required for
> >> + building everything:
> >> +
> >> + libpciaccess-dev
> >> + libdrm-dev
> >> + xutils-dev
> >> + libcairo2-dev
> >> + swig2.0
> >> + libpython3.3-dev
> >> + x11proto-dri2-dev
> >
> > I guess my gripe with this kind of thing is people always tend you use
> > distro specific package names. Can we somehow prevent it though?
>
> Another problem is that it's bound to get stale. I just listed all the
> stuff I needed to install when I tried to build igt on a semi-fresh
> debian based installation. My gripe is having to run ./autogen.sh N
> times, trying to figure out which package would fix the errors each
> time. If only there was an option to list the dependencies!
>
> I'm fine with not merging this. If anyone has better ideas, patches
> welcome. ;)
>
> BR,
> Jani.
>
>
I think it's better than nothing... just wanted to see if anyone had
better ideas. I just use the wrong package manager, I suppose. It is
definitely irritating that autofoo can't just create the list for us.
Also, a few of the deps you list are optional (though I think it makes
sense to do what you did, which is a default build).
--
Ben Widawsky, Intel Open Source Technology Center
next prev parent reply other threads:[~2013-10-09 14:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-08 18:19 [IGT PATCH] README: list some of the dependencies Jani Nikula
2013-10-08 23:11 ` Ben Widawsky
2013-10-08 23:50 ` Anca Emanuel
2013-10-09 7:09 ` Jani Nikula
2013-10-09 14:46 ` Ben Widawsky [this message]
2013-10-17 2:11 ` Ben Widawsky
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=20131009144625.GA13399@bwidawsk.net \
--to=ben@bwidawsk.net \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
/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