[MacPorts] #14537: tclsh does not have /Library/Tcl in its path
#14537: tclsh does not have /Library/Tcl in its path -----------------------------------------+---------------------------------- Reporter: shreevatsa.public@gmail.com | Owner: macports-tickets@lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Keywords: | -----------------------------------------+---------------------------------- The Tcl from MacPorts does not seem to have /Library/Tcl in its path, which, ironically, makes it harder to work with MacPorts. (For "package require macports", etc.) Example: {{{ $ echo 'puts $auto_path' | /opt/local/bin/tclsh /opt/local/lib/tcl8.5 /opt/local/lib $ $ echo 'puts $auto_path' | /usr/bin/tclsh /System/Library/Frameworks/Tcl.framework/Versions/8.4/Resources/Scripts /System/Library/Frameworks/Tcl.framework/Versions/8.4/Resources /usr/lib ~/Library/Tcl /Library/Tcl /Network/Library/Tcl /System/Library/Tcl ~/Library/Frameworks /Library/Frameworks /Network/Library/Frameworks /System/Library/Frameworks }}} -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/14537> MacPorts </projects/macports> Ports system for Mac OS
#14537: tclsh does not have /Library/Tcl in its path ------------------------------------------+--------------------------------- Reporter: shreevatsa.public@gmail.com | Owner: macports-tickets@lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Resolution: | Keywords: ------------------------------------------+--------------------------------- Comment (by raimue@macports.org): MacPorts' `/opt/local/bin/port` loads `/Library/Tcl/macports1.0/macports_fastload.tcl` explicitely. So this should not be a problem. As you compared to Apple's tclsh: Which of these paths should be added besides `/Library/Tcl`? -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/14537#comment:1> MacPorts </projects/macports> Ports system for Mac OS
#14537: tclsh does not have /Library/Tcl in its path ------------------------------------------+--------------------------------- Reporter: shreevatsa.public@gmail.com | Owner: macports-tickets@lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Resolution: | Keywords: ------------------------------------------+--------------------------------- Comment (by shreevatsa.public@gmail.com): Sorry, I don't know anything about Tcl; I don't know what paths should be added or to what variable (or else I would have submitted a patch instead :-)), but adding /Library/Tcl to auto_path seems to be sufficient to do "package require macports" in a Tcl script. -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/14537#comment:2> MacPorts </projects/macports> Ports system for Mac OS
#14537: tclsh does not have /Library/Tcl in its path ------------------------------------------+--------------------------------- Reporter: shreevatsa.public@gmail.com | Owner: macports-tickets@lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Resolution: | Keywords: ------------------------------------------+--------------------------------- Comment (by afb@macports.org): Replying to [ticket:14537]:
The Tcl from MacPorts does not seem to have /Library/Tcl in its path, which, ironically, makes it harder to work with MacPorts. (For "package require macports", etc.)
Normally one uses `/usr/bin/tclsh` (system version) for MacPorts ? For instance Perl and Python doesn't include system paths either... -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/14537#comment:3> MacPorts </projects/macports> Ports system for Mac OS
#14537: tclsh does not have /Library/Tcl in its path ------------------------------------------+--------------------------------- Reporter: shreevatsa.public@gmail.com | Owner: macports-tickets@lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Resolution: | Keywords: ------------------------------------------+--------------------------------- Comment (by shreevatsa.public@gmail.com): Yes, I can use the system version (or use the full path when loading a package). If it is MacPorts policy not to include system paths, then I guess this is an invalid bug, and can be closed. (I don't see the reason for the policy, though.) -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/14537#comment:4> MacPorts </projects/macports> Ports system for Mac OS
#14537: tclsh does not have /Library/Tcl in its path ------------------------------------------+--------------------------------- Reporter: shreevatsa.public@gmail.com | Owner: mww@macports.org Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Resolution: | Keywords: ------------------------------------------+--------------------------------- Changes (by jmr@macports.org): * owner: macports-tickets@lists.macosforge.org => mww@macports.org Comment: Assigning to maintainer. -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/14537#comment:5> MacPorts </projects/macports> Ports system for Mac OS
participants (1)
-
MacPorts