Hey, On Sun, 2005-11-27 at 08:40 -0800, Ken Mays wrote: > The other thing to consider with JDS is that we still have missing or > outdated gnome desktop applications. Secondly, we don't provide the > ease of transition to the latest available JDS (i.e. GNOME 2.10). > Third, no support for all currently > shipping Solaris releases (i.e. Solaris 8, 9).
o Yeah, there's always going to be missing or outdated GNOME applications - that's the nature of things in Solaris, but something I'm kinda hoping we might be able to change on OpenSolaris. While we are obviously limited by various timelines with Solaris, our work on OpenSolaris.org can continue apace. o What ease of transition are you looking for? More details would be appreciated. Eventually I want to get to the stage where it's really easy to install the latest and greatest set of builds available for the development GNOME work - we did hope to provide a set of binary packages for the GNOME 2.10 drop, but didn't get time. We'll definitely get this for 2.12. o Yeah, we probably won't have enough time/energy to backport this stuff to Solaris 8 and 9 - I'm not even sure that's something that we need to do however. I would have thought those people that are running 8 and 9 would probably appreciate more stability than downloading the latest and greatest packages. Would love to see some data on this. > With the pkgbuild, how will it be aligned with GARNOME so we can > provide as > much support to the GNOME on Solaris community as possible? An ISV may > want to go to a build script, point it to a directory of GNOME 2.13.2 > tarballs, and just press enter to build the entire GNOME sources from > scratch. No batteries required. We can log the results and then report > that info back to the GNOME developers for guidance and Sun. I see we > are doing that with the JDS build instructions and *.spec files. Yet, > you will always have the ISVs that want the 'bleeding-edge' versions > of GNOME/JDS from the developer/unstable branch (i.e. GNOME 2.13.2 > currently) and want something like a package build system like GARNOME > or pkgbuild to do the work for them. So, I'm not a big fan of GARNOME at all - I can see the uses, but I much prefer jhbuild. If you're going to build development snapshots of GNOME, you might as well use CVS. jhbuild is the GNOME community tool of choice. However, that being said, what we do plan to do is get to a stage with Solaris where rebuilding a given GNOME package [stable or unstable] is *really* easy - making sure that we have all the build requirement readily available. That'll help with using GARNOME/jhbuild or otherwise. Another thing that's in the pipelines is providing a Solaris machine to the GNOME Foundation to work as a tinderbox - that's in the works and I'll report back when I know more of the status. Glynn
