[macports-contrib] 02/02: port-whatsnew: remove -t option for macportsTclPath - it doesn't appear to do anything

[Rainer Müller]

On 2017-06-16 04:14, Kurt Hindenburg wrote:
> Kurt Hindenburg (kurthindenburg) pushed a commit to branch master
> in repository macports-contrib.
>
> https://github.com/macports/macports-contrib/commit/d4985c85db95aa3423d614985df6da996533d636
>
> commit d4985c85db95aa3423d614985df6da996533d636 Author: Kurt Hindenburg <kurt.hindenburg at gmail.com>
> AuthorDate: Thu Jun 15 22:14:56 2017 -0400
>
> port-whatsnew: remove -t option for macportsTclPath - it doesn't
> appear to do anything ---
>  port-whatsnew/port-whatsnew | 12 ------------
>  1 file changed, 12 deletions(-)
>
> diff --git a/port-whatsnew/port-whatsnew b/port-whatsnew/port-whatsnew
> index bb3c30f..3ac0d4c 100755 --- a/port-whatsnew/port-whatsnew +++
> b/port-whatsnew/port-whatsnew @@ -7,8 +7,6 @@ set MY_VERSION 0.2  proc printUsage {} {
>      puts "Usage: $::argv0 \[-hvV\] \[-t macports-tcl-path\] port-name"
>      puts "  -h    This help"
> - puts " -t Give a different location for the base MacPorts Tcl" -
> puts " file (defaults to /Library/Tcl)"      puts "  -v    verbose output"
>      puts "  -V    show version and MacPorts version being used"
>      puts ""
> @@ -18,7 +16,6 @@ proc printUsage {} {  
>  # Begin
>  
> -set macportsTclPath /Library/Tcl
This used to be the path where to find the macports1.0 tcl package,
which was necessary when you had multiple installations of MacPorts in
different prefixes for development. It is obsolete ever since we ship
our own Tcl installation. As all scripts are supposed to use
${prefix}/bin/port-tclsh as interpreter, which inherently already
selects the prefix.

Rainer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20170616/35311c9f/attachment.html>