Heads up: Movement of /usr/ccs/bin utilities to /usr/bin
Date: Mon, 25 Jun 2007 13:16:28 -0700
From: Lee Damico <lee.damico at sun dot com>
To: on-all at eng dot sun dot com, onnv-gate at onnv dot eng dot sun dot com
Subject: Heads up: Movement of /usr/ccs/bin utilities to /usr/bin
PSARC 2005/420 ~-- the movement of /usr/ccs/bin utilities to /usr/bin
~-- has been resurrected and integrated in Nevada build 68. This latest
putback is specific to the ON portion of the project (see 6319687).
The compiler owned portion integrated in build 42 (see 6249724).
With this update, it is no longer necessary to include /usr/ccs/bin
in your path. The exception is if you call either "admin" or "help"
directly rather than via "sccs admin" or "sccs help". These two
commands, owned by the compiler team, were not migrated to
/usr/bin with their putback."
How else will this affect you? It shouldn't unless you have an identically
named utility included in your search path that was previously before
/usr/ccs/bin but after /usr/bin. The ld command in /usr/ucb/bin is one
possibility. Another is gnu yacc in /opt/csw/bin.
In terms of ON builds, unless you do a full clobber build, you will also
need to remove the following files from your proto area to avoid
packaging warnings:
./usr/ccs/bin/gprof.callg.blurb
./usr/ccs/bin/gprof.flat.blurb
./usr/ccs/bin/nceucform
./usr/ccs/bin/ncform
./usr/ccs/bin/nrform
./usr/ccs/bin/yaccpar
These now live in the newly created /usr/share/lib/ccs. The bfu utility
has been updated to account for these as well. If you use a version other
than that provided in /ws/onnv-gate/public/bin or the latest onbld
package, you may want to manually remove the above files from the
old path, though there is no harm in leaving them in place.
Lee
on 2009/11/24 14:23