Dave Miner wrote:
> Ghee Teo wrote:
>   
>> Laszlo (Laca) Peter wrote:
>>     
>>> On Fri, 2008-08-08 at 15:34 -0400, Dave Miner wrote:
>>>   
>>>       
>>>> >> The recommendations are posted at:
>>>>     
>>>>         
>>>>>> http://www.opensolaris.org/os/project/indiana/cd_recommendations/
>>>>>>
>>>>>>         
>>>>>>             
>>>>> I saw SUWNgnome-pilot and SUNWpilot-link are planed to be removed, but
>>>>> they are run time dependency of SUNWevolution.
>>>>>
>>>>>       
>>>>>           
>>>> Sigh.  At least they're small.  Is there any reason they necessarily 
>>>> have to be dependencies of Evolution?  In other words, is this a design 
>>>> dependency or merely the way we configure our build of Evolution?
>>>>     
>>>>         
>>> Similarly, SUNWgnome-camera is a dependency of SUNWgnome-img-organizer
>>> (because gthumb can also import photos from your camera via gphoto2).
>>>
>>> Removing gdesklets is fine, I think, they never worked for me anyway (;
>>>
>>> Need to verify how gtk+ links to cups.  It has a cups printing backend
>>> but it will probably work fine without it.  Cc'ing Ghee to confirm.
>>>   
>>>       
>>    Unfortunately, removing libcups.so will cause the applications to 
>> exit when the GTK+
>> print dialog is brought up regardless of print system used at the time. 
>> So we can't remove
>> SUNWcups without further engineering work.
>>
>>     
>
> Can you estimate what portions of SUNWcups would need to be retained to 
> keep the print dialog functional?
>   
  My initial testing out showing that it needs libcups.so.* which is in 
SUNWcupsu to
run Print Dialog in lp. Printing group owns this package and Norm is CCed.

-Ghee
> Dave
>
> _______________________________________________
> indiana-discuss mailing list
> indiana-discuss@opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/indiana-discuss
>   


_______________________________________________
indiana-discuss mailing list
indiana-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/indiana-discuss

Reply via email to