[MacPorts] #43809: port selfupgrade to base v2.3.0 fails on G4
MacPorts
noreply at macports.org
Sat May 24 09:38:37 PDT 2014
#43809: port selfupgrade to base v2.3.0 fails on G4
--------------------------+--------------------------------
Reporter: paulccobb@… | Owner: macports-tickets@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: base | Version: 2.3.0
Resolution: | Keywords:
Port: |
--------------------------+--------------------------------
Comment (by paulccobb@…):
Many thanks for coming back quickly with these two replies. I had picked
up a new Tcl because I needed >=8.5 for something I was working on, but I
can live with it being somewhere other than /usr/bin, at least as a
temporary workaround.
I understand the point that you can't rely on any particular tlcsh path
and/or version in the early stages of the installation. Couple of quick
thoughts, for whatever they're worth:
1. Would it be possible to have the configure script do the search for a
tclsh as at present, BUT also do a quick sanity check of whether the Tcl
version is appropriate for the Mac OS version? If the check fails, exit
with a message explaining that the installation process needs Tcl
<major>.<minor> in /usr/bin (or wherever). Ideally the sanity check could
also consider architecture, and not try to use a 64-bit Tcl on a 32-bit
host (or vice versa).
2. Could there be a way e.g. a config option to specify the Tcl
interpreter for use during the installation, so that if I know I've got a
suitable Tcl somewhere on my machine, I can tell the MacPorts installer
about it?
I let the new Tcl go into /usr/bin only because that was the default for
the installer (think I used the package from ActiveState, but couldn't
swear to it), so I'd guess others will run into this same issue sooner or
later.
Again, many thanks for the explanations.
--
Ticket URL: <https://trac.macports.org/ticket/43809#comment:3>
MacPorts <http://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list