webrev suggestion
Kelly O'Hair
Kelly.Ohair at Sun.COM
Thu Feb 25 10:26:56 PST 2010
On 2/25/10 9:53 AM, Jonathan Gibbons wrote:
> Andrew John Hughes wrote:
>> On 25 February 2010 17:35, Jonathan Gibbons <Jonathan.Gibbons at sun.com>
>> wrote:
>>> In webrev, there is a function "look_for_prog". This is used to check
>>> the
>>> path and a number of other locations for individual programs. These
>>> other
>>> locations include /java/devtools and other Sun specific locations.
>>>
>>> It would be nice if the list of locations were configurable.
>>> Locations like
>>> /java/devtools can be problematic when automount and VPN is involved.
>>>
>>> -- Jon
>>>
>>>
>>>
>>
>> I concur with you that they should be configurable; that applies not
>> only to webrev but to the whole of OpenJDK. Those of us outside Sun
>> obviously don't have that /java hierarchy lying around (or even know
>> what it looks like, except by trial-and-error). I did think most of
>> them were.override-able though and webrev works fine here without
>> /java.
> Yes, I know webrev works without /java, but it doesn't work so well for
> those of us who have access to the Sun network via VPN. It's annoying to
> have to wait for automount delays for no obvious benefit.
>
> -- Jon
It would be my preference that dependencies be found via PATH and PATH
alone if at all possible.
This style of having a make variable for every tool, or baking in
site specific paths into scripts has never been my preferred way of
doing things. I understand some of the reasons why this was done, but
I would much prefer a PATH based scheme, if at all possible.
As soon as any full path enters the script picture, you end up with the
Windows hell of C:/ paths or /cygdrive/c/ paths.
Not that I'm volunteering to fix the world. :^(
-kto
More information about the jdk7-dev
mailing list