Heya,
> Looks cool, but brings a few questions to mind for me:
>
> So are you still planning to go to GNOME 2.10 first for JDS &
> OpenSolaris, or jump straight to 2.12?
So we've discussed this within the team quite a bit, and I think we all
more or less agree that we pretty much have 2.10 wrapped up - it's not
as stable or as polished as we'd like, but it's there and we think
there's probably enough demand to get packages out for it so that people
keen to install a newer GNOME on OpenSolaris can go for it. Obviously,
it'll be unsupported ;)
We have the following [simplified] CVS structure internally -
--------------------------------------- HEAD [currently Cinnabar Linux]
\
\-------- gnome-2-10
So the plan of attack is going to be -
o Merge any changes that we missed after branching for
gnome-2-10 from HEAD to gnome-2-10
o Create packages for 2.10 so that people can try it out
o Branch HEAD for cinnabar-linux [internal code name]
o Start working on 2.12 on HEAD
And further along, we're planning on a 'develop to HEAD' strategy, which
basically involves tracking community unstable on HEAD *all the time*,
and having packages available for people to easily develop with.
> Did we ever decide whether it should be the X packages or GNOME
> packages that deliver Cairo for Solaris?
I don't have huge issues with either - I know Brian Cameron has done a
certain amount of work getting Cairo to build and run on Solaris, so it
might be good to sync up with him? My slight worry with the Cairo stuff
is the ABI/API compatibility guarantees that we've given with GTK+ -
apparently the latest code exposes some Cairo API's before the API has
completely frozen....fun! ;)
> It looks like 2.12 may use the Xcursor library, which has been on
> our todo list, but not a high priority because no one told us they
> were ready to use it. Does this use libXcursor? Any other new
> X libraries we don't deliver yet but should?
Yeah, it does, but it's a conditional compile on it at the moment, so
probably no huge problems initially.
I haven't been able to keep in touch with the community code for 2.12,
so I don't know of any other cases where this might be a problem. Is
there any new X libraries that we should take a look out for?
Glynn
