On 09.09.2013 16:32, Johannes Obermayr wrote:
Do you guys actually read what I am writing and referring to or do you only see a big SR and patch?
No, at least i did read your emails and looked at the links.
Again the key fixes and improvements:
- bnc#833714 (OSMesa symbols)
- bnc#807205,rh#917687 (issue with already applied patch)
- Readd lost things to the follow-up patch, possibly lost due to merge conflicts
- Drop obsolete patches which could mess up things
- fdo#64810 (EGL runtime issue), could be also bnc#839074
- ~ 1/2 build time
- ~ 1/5 - 1/6 binaries and -debuginfo
If this gets upstreamed we'll take it with pleasure. At least i will ;-). Can't speak for anybody else of course.
Is the only reason you don't want them fixed in 13.1 because...
The reason i can imagine is: Do you know if something breaks? No, you can't. And breaking a key package that late in the release cycle is not a good idea. Maybe it would not break something, but it's really risky. And even after that, who will take care of these changes? If upstream changes something. You? Yes maybe for Mesa 10/11. But what if you lose interest? Can we go back to upstream or do we introduce a problem for later releases.
...they require 22 patches and upstream core devs don't want to talk to me anymore.
If they don't speak to you anymore, sorry. I don't know what happened, so i will not comment on this.
Maybe they change their mind if one of the big distribution ships them ...
You think? If they haven't taken the changes yet, for reason i don't know, they will not get convinced by downstream changes.
IMHO esp. maintainers should read comments and add a note to each proposed change why it won't be accepted.
Sorry to be a little harsh!