X11 code is still broken in various places, for example in Inferno-os (and even more so acme-sac, which is missing some of the updates that made it into inferno-os).
So my comment applies as much to the osx code as to the x11 code, and to hypothetical win32 code. That is the whole point, that every time there is a new port, the same dance starts over again, and even when code is 'mature' its maintenance in some systems (eg., p9p) is better than others (eg., inferno-os). If there was a single codebase shared across projects none of this would be an issue at all. uriel On Thu, Jul 3, 2008 at 5:30 PM, andrey mirtchovski <[EMAIL PROTECTED]> wrote: >> Is there any way we could solve the current state of affairs > > if that's the royal "we" you're using then sure, there is a way : > simply download the latest versions of all programs that you're > interested in unifying (p9p, drawterm, 9vx, acme-sac, inferno), merge > the osx drawing code (using the best solution available, which for > some things is 9vx, for others acme-sac, for thirds yet, p9p), > redistribute the new code to the respective maintainers and then track > each new release of the code (or periodically check) for changes to > redistribute. > > the only reason you're not in the same mess with the X11 code is that > the base everyone cloned was mature. >
