William Yang wrote:
>> Personally, I think there is value in delivering the devel packages and
>> the pc files. They are clearly in a private directory, so anyone who
>> uses them should know they are unsupported without a contract.
>>
>> Making it possible for people to build newer GTK+ based programs on S10
>> if they desire, even if in an unsupported fashion, will be a big benefit
>> to some people, I think. Also, it is much easier for other project
>> teams to use the interfaces with a contract if the -devel packages are
>> not delivered separately.
>>
>> Brian
>
> A big +1 (as a customer/sysadmin/software compiler)
We'll deliver -devel packages but they won't be supported in any way.
>
> If not already planned, can /usr/lib/gnome-private copies of libraries also
> search the main system GTK installation for theme files and engines so that,
> for instance, Firefox 3.5 or other programs linking against
> /usr/lib/gnome-private GTK also are able to use the same system themes (such
> as JDS Blueprint)?
The new libraries don't do that currently since we aren't including
upgraded version of SUNWgnome-themes. However I checked that this can
be achieved by creating links under /usr/lib/gnome-private/share for
/usr/share/{icons,themes,pixmaps} and under
/usr/lib/gnome-private/lib/gtk-2.0/2.10.0/engines for each of the
engines in /usr/lib/gtk-2.0/2.4.0/engines. This change looks like it
needs some testing and if we can't push this in the initial putback
itself, I'll open a bug to track it.
Thanks
Hemantha
>
> William Yang
>
