jdeps command
Michael Hall
mik3hall at gmail.com
Wed Apr 29 22:13:58 UTC 2015
On Apr 29, 2015, at 4:41 PM, David DeHaven <david.dehaven at oracle.com> wrote:
> My solution is to put this in ~/.profile and skip using the stub tools in /usr/bin:
Again, I have no problem with a user having their own fix in a startup shell script. Although, this one I might have to take a closer look at to completely understand what it’s doing.
But what about a distributed shell script? You would probably assume that anyone providing one for OS X would have tested on the platform.
But what if they try to write a generic Unix type script. It seems like most of those that I see prefer specifying /usr/bin/java rather than just ‘java’.
I just wonder if there wouldn’t be some way to have a platform wide mechanism. Build something in the java installer maybe that makes sure the complete set of /usr/bin links is there?
Or if scripts like this start getting to OS X with /usr/bin/jdeps they will break.
Michael Hall
More information about the macosx-port-dev
mailing list