On Thu, Jul 14, 2005 at 03:26:17PM -0700, Jake Hamby wrote: > are enabled). While you may argue that Linux developers are at > fault for using bash-specific features in their scripts, it's like
I wouldn't argue it, because it's a fact. It's fine for Linux to assume GNU features in /bin/sh. It's not fine for software that's intended to be portable. In fact the GNU project has very strict portability requirements, and others need to follow their example. If you want to write a bash script, that's fine; it starts with #!/bin/bash. Please submit fixes to maintainers of software assuming nonstandard /bin/sh. It won't get fixed otherwise. > Another symlink that we might discuss changing is /usr/bin/tar to > point to /usr/sfw/bin/gtar instead of /usr/sbin/tar. The main No. Please, not again. You'll wake up Joerg. This has come up before, and I hope it was archived last time. > feature of GNU tar not present in Solaris tar is built-in support > for .tar.gz and .tar.bz2 archives using the -z and -j flags, but I Would you consider working on a fix for this bug? Look for: 6267081 *tar* tar needs 'z' functionality > not *too* difficult to get used to typing gtar all the time, and I > couldn't guarantee that changing /usr/bin/tar would be 100% safe > from the POV of standards compliance and passing testsuites, or if > there are customers whose scripts depend on the current behavior of > /usr/bin/tar. It's not safe. The long filename issue is just one of the incompatibilities between the two. But if you fix the bug above, you'll probably not even be able to tell the difference between the two and won't care. -- Keith M Wesolowski "Sir, we're surrounded!" Solaris Kernel Team "Excellent; we can attack in any direction!" _______________________________________________ opensolaris-discuss mailing list [email protected]
