[Mesa-dev] [PATCH] build: Disable building of d3d1x

Kenneth Graunke kenneth at whitecape.org
Sat Sep 15 11:48:27 PDT 2012


On 09/07/2012 12:52 PM, Matt Turner wrote:
> On Fri, Sep 7, 2012 at 9:28 AM, Jose Fonseca <jfonseca at vmware.com> wrote:
>> ----- Original Message -----
>>> On Fri, Sep 7, 2012 at 3:30 AM, Jose Fonseca <jfonseca at vmware.com>
>>> wrote:
>>>> ----- Original Message -----
>>>>> On Thu, Sep 6, 2012 at 11:39 PM, Jose Fonseca
>>>>> <jfonseca at vmware.com>
>>>>> wrote:
>>>>>> Matt,
>>>>>>
>>>>>> I see you went ahead and just disabled it. Please remove it all
>>>>>> together.
>>>>>>
>>>>>> Touching code that is not built nor tested ends just silently
>>>>>> introduces bugs, so keeping this around won't help bring it back
>>>>>> one day in any way.
>>>>>>
>>>>>> Jose
>>>>>
>>>>> I talked with both Marek and Christoph, and they both said they'd
>>>>> prefer to simply disable the build. I don't feel strongly, but if
>>>>> someone is to revive it it'd be nice if we didn't make the git
>>>>> history
>>>>> harder to follow.
>>>>
>>>> I suppose they have their arguments, and I hope they include making
>>>> this build again shortly.  What I don't understand is why these
>>>> talks didn't happen within this email thread. I'd expect at least
>>>> a heads up email before committing this...
>>>
>>> I don't know why they didn't respond via email.
>>>
>>> It's not like we can't still remove d3d1x...
>>
>> Matt, Christoph, Marek, thanks for your replies.
>>
>> It doesn't sound like anybody plans to work on it on the immediate future, though it appears to be some faint wish to work on it eventually. So removing it now; or wait a little longer and removing it if nobody touches it, either is fine by me.
>>
>> Concerning other candidates for removal, it needs to be evaluated case-by-case.
>>
>> Jose
> 
> An option I haven't thought of until now is removing it from the 9.0
> branch, but leaving it in master at least for now.

That seems reasonable.  Any released version isn't useful.  Anybody
wanting to work on it would use master.  Saves reports about "hey, this
software you released doesn't work" -> "right, we know"

That said, I'd be fine with removing it from master too.  Don't really care.

> I'm okay with removing it. I'm not planning to convert its static
> Makefiles into automake.


More information about the mesa-dev mailing list