From: Keith M. <kei...@us...> - 2012-06-29 20:07:27
|
On 29/06/12 12:03, Chris Sutcliffe wrote: > > 2) A new '-2' release of the existing version, with the following patch > > applied: > > > > http://cygwin.com/cgi-bin/cvsweb.cgi/src/winsup/mingw/tlssup.c.diff?r1=1.4&r2=1.5&cvsroot=src > > > > 3) A new release from CVS. > > > > My personal preference is 3, followed by 2, then 1. > > Agreed, I will focus on creating a new mingwrt release based on CVS. > I'll also do a sweep of the bug reports, patches, etc. prior to making > the release. I should hopefully have it out in about a week. I'm still inclined to favour (2), as an interim step; remember that (3) will break ABI for any pre-compiled clients depending on dirent.[ch], so the next build from CVS should be at version 4.0, and not 3.21. The prime motivation for the ABI break, (besides fixing several POSIX non-conformances), was to support the new glob(3) API, which isn't yet in CVS, but can be found at http://tinyurl.com/cgkckca This will be a prerequisite to fixing aspect (2) of bug #3482704, (see http://tinyurl.com/clhlmu3), per http://tinyurl.com/cykazyx It would be kind of nice to include this glob(3) implementation, and its associated start-up code hooks, into an upcoming mingwrt-4.0, but Eli has raised some further concerns: http://tinyurl.com/bncxwpn I've been too busy, with day-job issues, to follow up on this, but I do think we need some further discussion before jumping in with an ABI breaking release, especially if there's a possibility we may want to break it again in the foreseeable future. -- Regards, Keith. |