On Tue, Mar 2, 2010 at 6:21 PM, Richard L. Hamilton <rlha...@smart.net> wrote: >> With the other non-standard changes being made to the >> default >> environment, I wonder if it is time to finally bite >> the bullet and merge >> some of the XPG4 and Sun commands -- some of the >> differences exist for >> some rather silly (IMO) semantic differences that >> portable code should >> not rely on. >> >> For example, rm differs in some very subtle ways >> about conflicts of -f >> and -i options, and handling of non-readable/writable >> directories. >> >> chown differs in the way symbolic links are followed >> in the presence of >> the -r flag. >> >> XPG4 awk is really just nawk. >> >> XPG4 grep has more flexible regular expression >> support (see -E and -F) >> >> who has slightly different default output for POSIX. >> >> XPG4 du is noisy by default on unreadable >> directories, and uses a space >> instead of a tab. >> >> I'm sure there are some others like this. >> >> I'm just thinking, isn't it time we just bit the >> bullet and told our >> users to start using the POSIX defaults, instead of >> continuing to supply >> the legacy compatibility stuff forever. >> >> It would save a little space, and maybe we could get >> rid of /usr/xpg4/bin ? >> > > While I don't know that I'd go that far, I think gawk is one of the (IMO all > too few) > examples of a really good GNU implementation: the developers worked > with the original awk developers (from what I've read) to get clarification > on a lot of compatibility issues. And gawk doesn't fall over on long lines > or huge numbers of fields per line like the other implementations do. > > Is there any particular reason why gawk (named awk or nawk) couldn't > replace both /usr/xpg4/bin/awk and /usr/bin/nawk?
I know one: It is currently unclear if an interpreter with a GPL v3 license requires the scripts to use a GPL v3 license, too. I attached a mail from caiman: ---------- Forwarded message ---------- From: Aaron Williamson <aarwilliam...@googlemail.com> Date: Fri, Feb 26, 2010 at 7:11 PM Subject: [caiman-discuss] Code review feedback for shell scripts for the Device Driver Utility(DDU) changes for Driver Update To: Shawn Walker <swal...@opensolaris.org>, caiman-disc...@opensolaris.org This is where you are wrong. If your script relies on features specific to GNU coreutils you create identical case as link dependency and thus your script requires a GNU General Public License v3 header (or compatible license), not a CDDL. High-Gain Antennas (case 07-CV-10455), Xterasys (case 07-CV-10456), Bell Microproducts (case 08-CV-5270), Super Micro Computer (case 08-CV-5269) etc. suffered from the same misunderstanding and accepted the consequences. This is CLEARLY spelled out in the cases and settlements. You have two choices: 1) Add GNU General Public License v3 header, replacing the CDDL header 2) Remove the use of unique GNU coreutils features in your script If you do nothing then you violate the GNU General Public License v3 and have to take the consequences (case numbers above are included as reference how these consequences look like). On Fri, Feb 26, 2010 at 5:38 PM, Shawn Walker <swal...@opensolaris.org> wrote: > On 02/26/10 07:24 AM, Aaron Williamson wrote: >> >> + for f_i in `/usr/gnu/bin/find -type f`; do >> >> The scripts which rely on features specific to GNU coreutils require a >> GNU General Public License v3 header, not a CDDL. > > No, it doesn't. > > -- > Shawn Walker > _______________________________________________ caiman-discuss mailing list caiman-disc...@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/caiman-discuss -- Jennifer Pioch, Uni Frankfurt _______________________________________________ opensolaris-code mailing list opensolaris-code@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
