Nevada build 85 (X packages available for testing now [internally only, sorry])
will have:
- xscreensaver with Sun logos in separate files so that it
can be redistributable without trademark issues and so that
Indiana branding can be done by delivering two replacement xpm files
- libX11 based on the open-source X11R7 sources with the i18n
changes from our G11n team and the changes needed to preserve
Solaris binary compatibility, so it can be redistributed as well.
It will however break compatibility with existing Indiana/FOX
binaries by going back to the libX11.so.4 SONAME that Solaris
uses. Hopefully instead of causing GNOME to rebuild, this will
allow use of the Nevada GNOME packages.
- X11R7/open-source/redistributable versions of:
libICE xev
libSM xlsclients
xauth iceauth
twm luit
xfd viewres
oclock
- Fixes for the fc-cache corruption bugs that occasionally cause
GNOME sessions to crash on login.
- FreeType upgraded from ancient version to current community 2.3.5
- Intel graphics driver updated to version 2.2.1 from Intel/X.Org
- fonts.conf updates for deliveries planned by G11n teams
- scanpci PCI id database updated from 2007-01-18 snapshot to 2008-02-28
- Composite extension on by default in Xorg (part, but not all, of what
would be needed for compiz on by default)
Planned/in progress for Nevada build 86:
- X11R7/open-source/redistributable versions of:
libXt
libXext
libXevie
libXscrnsaver
xterm
This should complete the most needed X11 libraries, making the
Nevada ones redistributable & the FOX ones using the same sources,
and ensure binary compatibility between Solaris & Indiana.
- Updates to X consolidation package Copyright files to incorporate
license data from the components for which a license file is included
in the upstream distribution. (i.e. some, but not all)
What's next/questions:
- Providing updated information about which X packages can be taken
directly from Nevada (either in whole or in part) for nv_85, and
possibly doing so under the new package names we've discussed.
I assume the preferred way of doing this is updates to the distro-import
files like the ones I've seen David recently post for the nv_83
resync - can someone point me to instructions on how to build my own
test image so I can test these before sending them to you? (I'm
guessing it also involves making my own repo, right?)
--
-Alan Coopersmith- alan.coopersmith at sun.com
Sun Microsystems, Inc. - X Window System Engineering
