[MacPorts] #28193: output to stderr should not make "port load" fail
MacPorts
noreply at macports.org
Thu Feb 3 17:43:59 PST 2011
#28193: output to stderr should not make "port load" fail
----------------------------------+-----------------------------------------
Reporter: vinc17@… | Owner: macports-tickets@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: base | Version: 1.9.2
Resolution: | Keywords: tiger
Port: |
----------------------------------+-----------------------------------------
Comment(by vinc17@…):
Replying to [comment:11 dluke@…]:
> Replying to [comment:9 vinc17@…]:
> > Replying to [comment:8 dluke@…]:
> > > patch?
> >
> > I don't know very much about tcl,
>
> well, you said the fix was easy :-)
For someone who knows tcl (I know to do this kind of things in Perl or C).
> > Is there any reason to use /usr/bin/tclsh instead of just tclsh?
>
> If you depend on the macports-provided tclsh, what happens when you try
to upgrade it (hint - it's bad), or if you deactivate it (also bad)?
It could depend on the macports-provided tclsh for some features only. The
version in /usr/bin/tclsh should be sufficient as a fallback.
> Of course, given that Apple isn't providing security updates for 10.4
any more - anyone running it should probably move to 10.5 any way.
I won't upgrade to 10.5 because some of my hardware is incompatible with
it. Then perhaps a solution would be to install a more recent tcl version
in /usr/local. But that won't solve the problem if MacPorts hardcodes the
path to /usr/bin/tclsh.
--
Ticket URL: <https://trac.macports.org/ticket/28193#comment:15>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list