Hi, Dan,

 >> Can I assume we're talking about w3m-0.5.2 or higher?
 
yes.

 >> Presumably you will amend the case and remember to record
 >> a package dependency on SUNWlibgc.

Thanks. Will fix this.

 >>  Given the use of libpng/gtk, am I to assume that you are enabling the
 >> optional image rendering support?  (--with-imagelib ?)  I'm skeptical
 >> that this is useful, and means that w3m might not be able to be
 >> used on a system which has no X11/GTK packages.

Actually this is enabled by default.

 >> I would also note (although it is not architectural) that libgc has 
worked
 >> poorly for me on x86, and led me to drop my usage of w3m (after about 6
 >> years) for elinks.

We are shipping this because tracker, a desktop search tool, depends on w3m.
I will add this info into materials.

-rick

>> Dan Price wrote:
>>> On Tue 27 May 2008 at 08:44PM, Shi-Ying Irene Huang wrote:
>>>  
>>>> Template Version: @(#)sac_nextcase 1.66 04/17/08 SMI
>>>> This information is Copyright 2008 Sun Microsystems
>>>> 1. Introduction
>>>>     1.1. Project/Component Working Name:
>>>>      W3M
>>>>     1.2. Name of Document Author/Supplier:
>>>>      Author:  Rick Ju
>>>>     1.3  Date of This Document:
>>>>     27 May, 2008
>>>> 4. Technical Description
>>>> 1. Introduction
>>>>    1.1. Project/Component Working Name:
>>>>
>>>>         w3m  a text-based WWW browser
>>>>     
>>>
>>> [Insert obligatory plug for 'elinks', which is better.  Oh well.]
>>>
>>> Can I assume we're talking about w3m-0.5.2 or higher?
>>>
>>> One concern I have is that the last time I built w3m, at least, it
>>> had a dependency on libgc (the Boehm Garbage Collector).  I take
>>> it that this case has a dependency on LSARC/2008/068?
>>> Since libgc was not listed in imported interfaces, I'm confused.
>>> Presumably you will amend the case and remember to record
>>> a package dependency on SUNWlibgc.
>>>
>>> Given the use of libpng/gtk, am I to assume that you are enabling the
>>> optional image rendering support?  (--with-imagelib ?)  I'm skeptical
>>> that this is useful, and means that w3m might not be able to be
>>> used on a system which has no X11/GTK packages.
>>>
>>> I would also note (although it is not architectural) that libgc has 
>>> worked
>>> poorly for me on x86, and led me to drop my usage of w3m (after about 6
>>> years) for elinks.
>>>
>>>
>>>  
>>>>      Table rendering algorithm in w3m
>>>>     
>>>
>>> This text seems entirely out of scope for a case like this.  Also, you
>>> copied it verbatim from the documentation of w3m (doc/STORY.html) 
>>> without
>>> attribution.  That seems bad.
>>>
>>>         -dp
>>>
>>>   
>>
>


Reply via email to