> > There's also a theoretical problem. Probably no such thing really > > exists, but let's say we have Solaris libfoo in /usr/lib and > > GNU libfoo, which is implemented in c++. Which build goes > > into /usr/gnu/lib g++ or Forte? Where do we put the other one? > > It doesn't solve the two-by-two case, true. Is there an example of > this you can think of?
Nope. Like I said, it's unlikely to exist. So I'm fine with /usr/gnu if everyone (well, PSARC) thinks it's okay. > (Another approach would be to not use > directories, but a filename convention, like libgtkmm_abi2 (as was > done for hardware capabilities in libc).) A directory based approach is a lot easier to implement and use. Laca
