./shells/mksh, MirBSD Korn Shell

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ] [ Add to tracker ]

Branch: pkgsrc-2008Q1, Version: 33d, Package name: mksh-33d, Maintainer: pkgsrc-users

mksh is the MirBSD enhanced version of the Public Domain Korn shell
(pdksh), a Bourne-compatible shell which is largely similar to the
original AT&T Korn shell. It includes bug fixes and feature improvements
in order to produce a modern, robust shell good for interactive and
especially script use.

Master sites: (Expand)

SHA1: e1ab5c7897b7f91ab0dcd5be49ded8b441136291
RMD160: d810a705b01e146f9addd184c168798a22a36d38
Filesize: 249.913 KB

Version history: (Expand)

CVS history: (Expand)

   2008-04-22 17:34:00 by Tyler R. Retzlaff | Files touched by this commit (2) | Package updated
Log message:
pullup ticket #2336 - requested by wiz
updated package fixes a security problem

Revisions pulled up:
- pkgsrc/shells/mksh/Makefile	1.7
- pkgsrc/shells/mksh/distinfo	1.7

   Module Name:	pkgsrc
   Committed By:	wiz
   Date:		Thu Apr 17 05:55:50 UTC 2008

   Modified Files:
   	pkgsrc/shells/mksh: Makefile distinfo

   Log message:
   Update to R33d:

   No changes in mksh R33c except for Ultrix support. None in R33d.

   In mksh R33b, much more compilers are detected, even if not all of
   them are supported. The OE (OS and CC/LD) versions are now dumped
   too. Instead of #error, forced link failures are now used as the
   mechanism to auto-detect some things in the target environment.
   Features are now much better detected, and some annoying warnings
   don't show up any longer due to this.  Less tools are required to

   Please be reminded that you should run ./test.sh -v inside an
   environment with /dev/tty available (as device node) and usable
   (e.g. use script(1) or GNU screen if you're doing auto-builds
   detached from controlling terminal). Use -v to see failures.

   No surprises in mksh R33 either, but the build system now gives
   more detailed output on the version actually built, to aid tracking
   down FTBFSen (build errors) with access to only the build logs.
   Regression tests now work with Intel's compiler on SLES too, which
   requires a custom LD_LIBRARY_PATH formerly stripped by the script.