On 2009-03-10 at 20:36:20 [+0100], Rene Gollent <anevilyak@xxxxxxxxx> wrote: > On Tue, Mar 10, 2009 at 1:57 PM, Ingo Weinhold <ingo_weinhold@xxxxxx> wrote: > > > > I'm wondering, does anyone see problems with switching to a new libroot > > while still shipping a compatibility libroot? After all the only reason > > for > > using the current glibc mishmash is for binary compatibility with BeOS. > > > > Are you suggesting keeping old libroot around for bin compat and > having a new lib with a different name going forward? If so, I'd be > all for that myself. Not even a new name. I would simply stash the compatibility libroot somewhere out of the way and let the runtime loader load it when necessary. I guess we should add some tag to our glue code, so that the runtime loader can easily find out which Haiku version a shared object was built with. If we're planning for long-time compatibility something like this will be needed anyway. CU, Ingo