2011/9/30 Jeremy Huddleston :
>> Er, sure, but that brings up my second point: the GPL restricts
>> redistribution, not use, so you are not required to "accept it" to use
>> GPL tools.
>
> Again, mirroring Alan's comment. IANAL. I just do what the Lawyers
> say. I am told not to touch GLPv3 wit
2011/9/29 Alan Coopersmith :
>> _Why_ is the GPLv3 "not acceptable", when the GPLv2 was?
>
> Note his employer, which is well known as not accepting the GPLv3,
> possibly due to it being a mobile phone manufacturer, and the GPLv3's
> free patent license grant not fitting well with the current mobil
On , Matt Turner wrote:
> In short, 2.62 is the first version that includes GPLv3 tools to build
> autoconf, even though what is installed is GPLv2.
>
> [1] http://lists.x.org/archives/xorg-devel/2011-June/022724.html
Thanks, that explains the significance of 2.62 -- but it doesn't
actually expla
Gaetan Nadon writes:
> - The minimum autoconf version should be 2.60. Features above 2.60
> should not be used. Starting v 2.62 there is a license controversy
What is that?
[The NEWS file doesn't show any license changes in 2.62. Autoconf
itself switched to the GPLv3 in 2.65, but I'm not sure w
Eric Anholt writes:
> That's hard, because floating point framebuffers are so useful (and
> obvious).
... and so undeserving of patent protection ... :[
-miles
--
Corporation, n. An ingenious device for obtaining individual profit without
individual responsibility.
___
Matt Turner writes:
> Although, after cmake, if we just added an imake build system, I think
> we'd have everything covered.
I'm not sure it's possible to run out of build systems ... pretty much
everybody has written one!
-miles
--
Saa, shall we dance? (from a dance-class advertisement)
___
Jose Fonseca writes:
> And to be honest, WINE developers did a disservice to themselves by
> openly stating their concerns. They put themselves between the rock
> and the wall with that. For future reference, if people have this sort
> of doubts, they should contact the project maintainers (e.g Br
Ian Romanick writes:
>> How about putting "generated" files like that into a separate
>> subdirectory (e.g. ".../prebuilt"), which is ignored by the non-windows
>> builds?
>>
>> Then on windows, it can simply do "cp .../prebuilt/foo .../foo" instead
>> of generating the file using bison or whatev
Ian Romanick writes:
>> These files generated by bison and flex are different for me than the
>> ones checked in to git:
>>
>> src/glsl/glcpp/glcpp-lex.c
>> src/glsl/glcpp/glcpp-parse.c
>> src/glsl/glcpp/glcpp-parse.h
>> src/glsl/glsl_lexer.cpp
>> src/glsl/glsl_parser.cpp
>>
>> This is causing som
