Bart Smaalders wrote: > Roland Mainz wrote: > > Glenn Fowler wrote: > >> On Thu, 28 Jun 2007 03:54:46 +0200 Roland Mainz wrote: > >>>> readlink > >>> Erm... I missed this part... GNU "readlink" collides with the AST > >>> "readlink" command and the ksh93 builtin version... is there still a way > >>> to move this to /usr/gnu/ ? > >> ast doesn't have a readlink command ... > > > > No, but we added one few months ago to our side of the tree (and I wish > > we would've ARC'ed it immediately with PSARC 2006/550 ... than we > > wouldn't have the scratch-other-people's-eyes-out about this item... ;-( > > ) ... ;-/ > > Could someone please explain why conflicts w/ shell-builtins are important?
If the conflicting commands are not compatible (which is at least the case for the "stat" builtin) then they cannot be enabled and bound to a path by default. Right now we already have this kind of problem with many of the ksh93 builtin commands because they implement strict POSIX behaviour while their Solaris counterparts in /usr/bin/ have pre-POSIX behaviour (e.g. PSARC 2006/550 only enabled thos builtins which are 100% compatible between Solaris and POSIX/AST. A later case may look at binding the conflicting commands to /usr/xpg6/bin/ or /usr/xpg4/bin/ but that still makes it tricky to write portable shell scripts which should still be able to run on Solaris). And that had ruined much of ksh93 benefits for Solaris (and while I am throwing stones... AFAIK most of these cases were avoidable many years ago if more attention would be paid to the standards... ;-( ) ... ;-( > After all, we already have conflicts with kill, pwd, limit, ... Yes, but some of these builtins are "special builtins" defined by the POSIX shell spec and cannot be turned off. The problem in the case above is different - we have builtins which were excluded from PSARC 2006/550 to keep the ARC case "simple" and now we're bitten by PSARC 2007/048 and will never be able to enable the matching ksh93 builtins unless we get rid of the GNU squatters in /usr/bin/. Ok... back to the tracks... ... if I recall the discussion about the /usr/gnu/bin/ ARC case correctly GNU commands need to reside in /usr/gnu/bin/ if their location in /usr/bin/ is "disputed". And I am "disputing" that place now for the "stat" and "readlink" builtins (and for "open", "close", "poll" which were explicitly developed for the ksh93-integration project on Sun's request (there aren't matching GNU tools for these right now but I am listing them for completeness...)) - claws raised and ready to fight... ---- Bye, Roland -- __ . . __ (o.\ \/ /.o) roland.mainz at nrubsig.org \__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer /O /==\ O\ TEL +49 641 7950090 (;O/ \/ \O;)
