Erast,
It's reassuring to hear that my comment about compatibility wasn't taken
as a completely unachievable. Thank you for pointing out some details
of your efforts in this direction. I agree with Eric and Adam that
there can be good reasons for opensolaris distributions which aren't
compatible with 100% of the applications on other distributions.
Embedded Opensolaris might want to leave nearly all of the convenience
libraries out. But it would be nice to minimise the se
incompatibilities. Nexenta is potentially a bridge to the debian world
which seems to be the linux distribution with the strongest focus on API
stability. How much can we standardize between Nevada, Nexenta and
Linux based debians such that an application developer can "write once
and run almost everywhere?" Will it ever be possible for a user to
download a "pure opensolaris" application binary (package format TBD
;-) and guarantee that it will work on Schillix, Nexenta and Sun's
distribution or should we count on Java to be the only only stable cross
platform/cross distribution ABI?
I apologize for choosing the wrong forum to start this topic, but it
seems to encompass more than just the desktop. My example was an X11
lib incompatibility, but it could just as easily been something else.
Glibc seems to be a common source of incompatibilities between linux
distributions and we certainly don't want to go down that route.
Erast Benson wrote:
On Wed, 2005-11-30 at 15:24 -0800, Alan Coopersmith wrote:
Brian Nitz wrote:
I have a Nexenta elatte "gnusolaris" partition alongside my NV_27a with
a GNOME 2.12 JDS build. Nexenta is based on the same kernel code and
also contains a GNOME 2.12 desktop. Unfortunately the binaries for the
gnusolaris versions of these applications aren't easily interchangable
with the binaries in Nevada. For example when I try to run gnusolaris
zenity on Nevada, it fails because it expects libXi.so.6 and we have
libXi.so.5. If I set LD_LIBRARY_PATH to include /gnusolaris/usr/lib
and /gnusolaris/lib, the gnusolaris binaries run O.K. I was also told
that libXi.so.6 and libXi.so.5 are probably the same library with a
different name!
The real solution for that specific problem is to get all the distributions
using the same source for X libraries - unfortunately, that's currently
impossible, as Sun Solaris uses a X code base that's closed source and would
break binary compatibility with older Solaris versions if we just cut over
to the Xorg open source release. I really am working to get as much as we
can of Solaris X released via OpenSolaris as soon as possible (and libraries
like libX11 and libXi won't be in the first set of code released), but
unfortuantely have a day job competing with that work, so it's going slower
than anyone wants.
Here is some more information on this library:
http://www.gnusolaris.org/archive/elatte-unstable/x11/libxi6
% dpkg -s libxi6
Package: libxi6
Status: install ok installed
Priority: optional
Section: x11
Installed-Size: 41
Maintainer: Daniel Stone <[EMAIL PROTECTED]>
Architecture: solaris-i386
Source: libxi
Version: 1:1.3.0-2
Depends: libgcc1 (>= 1:3.4.4), libx11-6, libxext6, sunwcslr, x-common
Description: X11 Input extension library
libXi provides an X Window System client interface to the XINPUT
extension to the X protocol.
.
The Input extension allows setup and configuration of multiple input
devices,
and will soon allow hotplugging of input devices; to be added and
removed on
the fly.
.
More information about X.Org can be found at:
<URL:http://xorg.freedesktop.org>
<URL:http://lists.freedesktop.org/mailman/listinfo/xorg>
.
This module can be found as the module 'lib/Xi' at
:pserver:[EMAIL PROTECTED]:/cvs/xorg
Nexenta's Xorg using 6.8.2 + CVS HEAD fixes. I guess, once Solaris will
move to Xorg 7.0, this problem will be resolved.
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
