I'm sorry but making --text the default on a windows systems simply does not
make sense
it renders tgz md5sum verification useless
where do you see anywhere "the md5sum --binary value for foo.tgz is
hexhhexhexhex"
my guess is that because of this weasling
Note: There is no difference between binary and text mode option on
GNU system.
most gnu weaned users call md2sum with neither --text nor --binary
and this note lies anyway -- it *does* make a difference ' ' is printed for
text,
'*' is printed for binary
and on cygwin guess what -- md5sum defaults to binary
if there's any change it will be for the md5sum-specific output to do the ' '
vs '*'
based on text vs binary so on all implementations '*' will be printed by default
how many scripts will break with that default?
On Wed, 25 Sep 2013 00:39:18 +0200 Roland Mainz wrote:
> --089e01536feea09e6e04e728ceb8
> Content-Type: text/plain; charset=ISO-8859-1
> Hi!
> ----
> Attached (as "astksh20130913_md5sum_compat1.diff.txt") is a patch
> which fixes an incompatibility between AST md5sum(1)&&co. and GNU
> coreutils md5sum(1)&&co. fixes.
> There are three major differences which caused hiccups for 3rd-party scripts:
> - GNU coreutils md5sum/sha1sum/sha224sum/sha256sum default to text mode
> - GNU coreutils use a " *" before the file name to indicate binary
> mode and " " to indicate text mode... the AST hash utilities used
> only a single blank " " instead.
> - "-t" means "text mode" for GNU coreutils while AST used this for "total"
> * Notes:
> - GNU and AST *sum(1) utilities now have identical output and seem to
> be 100% compatible with each other
> - On platforms which do not implement |O_BINARY| and |O_TEXT| the
> change only affects the seperator (" "/" *"(=new) vs. " "(=old)).
> Portable applications can use [[:space:]]+ in egrep(1) to make sure
> they can match the hashes against both the old and new versions of AST
> *sum(1)
> - The output *intentionally* changes only for utilities matching the
> shell pattern "*@(md5|sha@(1|224|256|384|512))sum". This is done to
> maintain compatibility for cksum(1) and sum(1)
> - AST does not have a sha224sum(1) utility (yet) ... need to talk to
_______________________________________________
ast-developers mailing list
[email protected]
http://lists.research.att.com/mailman/listinfo/ast-developers
