From: Jani Nikula <jani.nikula@intel.com>
To: Petri Latvala <petri.latvala@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [i-g-t PATCH] README: add libkmod-dev and libprocps3-dev to dependencies
Date: Mon, 02 Jan 2017 15:50:08 +0200 [thread overview]
Message-ID: <87pok5inan.fsf@intel.com> (raw)
In-Reply-To: <20170102110108.4izyh7y4ww2hze3o@platvala-desk.ger.corp.intel.com>
On Mon, 02 Jan 2017, Petri Latvala <petri.latvala@intel.com> wrote:
> On Fri, Dec 23, 2016 at 10:12:17AM +0200, Jani Nikula wrote:
>> The list is perpetually out of date, but giving an idea of what the
>> dependencies are is helpful.
>>
>> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>> ---
>> README | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/README b/README
>> index d302af3f15dd..78a0a244d0ba 100644
>> --- a/README
>> +++ b/README
>> @@ -136,7 +136,9 @@ everything (package names may vary):
>> gtk-doc-tools
>> libcairo2-dev
>> libdrm-dev
>> + libkmod-dev
>> libpciaccess-dev
>> + libprocps3-dev
>> libunwind-dev
>> python-docutils
>> x11proto-dri2-dev
>> --
>> 2.1.4
>
> s/libprocps3-dev/libprocps-dev/
>
> procps package name on Debian is just libprocps-dev. Ubuntu has
> libprocps3-dev but only on 14.04, and even there the package
> provides:libprocps-dev.
>
> With that bikeshed change,
> Reviewed-by: Petri Latvala <petri.latvala@intel.com>
It's libprocps3-dev also on Debian, and it provides libprocps-dev. But
the change makes sense. Pushed.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2017-01-02 13:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-23 8:12 [i-g-t PATCH] README: add libkmod-dev and libprocps3-dev to dependencies Jani Nikula
2017-01-02 11:01 ` Petri Latvala
2017-01-02 13:50 ` Jani Nikula [this message]
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=87pok5inan.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=petri.latvala@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 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.