[Xcb] libX11 release
Josh Triplett
josh at freedesktop.org
Tue Jun 6 19:00:06 PDT 2006
Ian Osgood wrote:
>
> On Jun 6, 2006, at 5:13 PM, Donnie Berkholz wrote:
>
>> Josh Triplett wrote:
>>> Of the bugs currently blocking XCB 1.0, only 6798 ("Doesn't currently
>>> handle 32-bit wrap in sequence numbers") makes me concerned about
>>> releasing an Xlib which uses XCB by default. I also have some concerns
>>> about changing the SONAME of a library libX11 depends on; we plan to
>>> switch from libXCB.so.0 to libXCB.so.1 when we remove all the deprecated
>>> functions and release XCB 1.0. Other than that, I'd feel quite
>>> comfortable with Xlib/XCB by default on end-user systems.
>>
>> Library major version bumps happen, and they're not that bad to deal
>> with, just mildly annoying. FreeType in particularly is really good at
>> breaking backwards compatibility, but X manages to depend on it and deal.
>>
>> What I'm getting out of this discussion is that we can release
>> Xlib/XCB if:
>>
>> - The deprecated function(s) get(s) removed
>> - The 32-bit wrap gets fixed, and you push out a 0.9.1.
>>
>> Thanks,
>> Donnie
>
> Actually, these are the same problem, aren't they? The wrapping bug
> is due to using the deprecated XCBGetQueuedRequestRead
> in _XGetXCBBuffer() in xcl/xcblock.c.
No, XCB itself needs to handle 32-bit wrap; currently it asserts in
XCBSendRequest:
> request = ++c->out.request;
> assert(request != 0);
I think the same non-wrapping assumption occurs elsewhere in XCB.
> There is also one more Xlib/XCB bug recently found (7035) we
> should fix before release, if we want anybody to start porting apps
> from Xlib to XCB.
Ouch, yes, definitely.
- Josh Triplett
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 252 bytes
Desc: OpenPGP digital signature
Url : http://lists.freedesktop.org/archives/xcb/attachments/20060606/a787297e/signature.pgp
More information about the Xcb
mailing list