On Tue, Mar 10, 2009 at 3:43 PM, Ingo Weinhold <ingo_weinhold@xxxxxx> wrote: > > 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. Even better :) > > 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. > I'm assuming that mechanism would only be relevant to actual Haiku releases? Regards, Rene