[Piglit] [RFC] Piglit tags/releases
jljusten at gmail.com
Mon Sep 29 20:14:13 PDT 2014
On Mon, Sep 29, 2014 at 7:39 PM, Matt Turner <mattst88 at gmail.com> wrote:
> On Mon, Sep 29, 2014 at 6:45 PM, Jordan Justen <jljusten at gmail.com> wrote:
>> On Mon, Sep 29, 2014 at 5:01 PM, Matt Turner <mattst88 at gmail.com> wrote:
>>> On Mon, Sep 29, 2014 at 4:52 PM, Jordan Justen <jljusten at gmail.com> wrote:
>>>> Anyway, I discussed it with Ian around Mesa 10.2. While I don't think
>>>> he was excited about it, he also did not express any reasons for not
>>>> doing it. Basically, we were going to look at it again around Mesa
>>>> 10.3 release time.
>>> How about some reasons to actually do it? I still haven't figured out
>>> what you're trying to accomplish.
>> I'm planning to create a debian piglit package. (Well, it's basically
>> created at this point.)
> But to what end? Why is packaging snapshots of an always changing
> developer test suite useful?
1. I've wanted to just install (without building) piglit a couple of
times within the past year. In these cases, I just wanted to run
shader_runner on a single shader_test.
2. apt-get build-dep piglit will install the build dependencies for
building piglit from master.
More information about the Piglit