OpenGL/GLX dual link error in VLC 2.2.0 git/master via MacPorts on OS X
Jean-Baptiste Kempf
jb at videolan.org
Sat Feb 7 04:23:36 PST 2015
On 07 Feb, René J.V. Bertin wrote :
> On Saturday February 07 2015 12:41:37 Jean-Baptiste Kempf wrote:
>
> > > Good luck with that. My experience with that track is that they will just close your ticket and tell you to piss off.
> >
> >
> > Where did we ever tell you to "piss off"? Who insulted you? When?
>
> Matter of speaking and a personal impression undoubtedly, but I must say I concur with Jeremy that it's the impression one can get, given how some of my own tickets have been handled up to now.
No, it's not the same. It's a very clear difference between insults and
saying the fix is not the correctly wanted.
Moreover, I pointed at facts, and tickets numbers.
2 debated tickets out of 10 ?
And Jeremy reopend tickets when clearly asked to not reopen without more
info?
> > All other platform maintainers understand that, except Macports.
>
> No, I don't think that's true. At MacPorts we have to find and walk a fine line, but our needs are comparable to Fink's, HomeBrew's and a few lesser known others, and together we do represent a large enough movement that our needs cannot just be waved off because we don't do everything the exact Mac way, or (in this case), because we happen to have X11 stuff available.
It's funny how VLC on Brew works fine and is used, notably by tomahawk
(pure Qt application) and we never ever had a problem with them.
We have numerous patches from all BSD, most Linux distributions, Windows
and so on, and all of them get merged, with the very notable exception
of MacPorts.
> Please note that I have been asking from the beginning to find a proper fix for this regression (which, again, didn't exist in 2.1.5), or help to figure out what goes wrong, and why. Telling me that I shouldn't have the issue in the first place, while true in itself, isn't very helpful...
Sorry, but what regression?
> Of course I can also find a more hackish fix, like the fix I used to build against Qt4 instead of Qt5, but giving us the impression that we're on our own if we don't follow your build recipe exactly (because we can't) will only discourage us from sharing proper patches.
You can't use bootstrap, and configure?
With my kindest regards,
--
Jean-Baptiste Kempf
http://www.jbkempf.com/ - +33 672 704 734
Sent from my Electronic Device
More information about the macports-dev
mailing list