[MacPorts] #41656: Update Go Portfile to 1.2
MacPorts
noreply at macports.org
Fri Dec 27 13:54:16 PST 2013
#41656: Update Go Portfile to 1.2
---------------------+-------------------------
Reporter: b@… | Owner: ciserlohn@…
Type: update | Status: closed
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: fixed | Keywords: haspatch
Port: go |
---------------------+-------------------------
Comment (by larryv@…):
Replying to [comment:9 quest@…]:
> That makes sense, but if you do it as a separate port, would it be
> locked on a particular SHA, or would it just build the latest within
> the go 1.2 branch? Seems the issue the maintainer brought up on
> code.google.com still wouldn't be addressed. The package could change
> whenever someone commits to that branch.
The new port would have to be fixed to a specific changeset. The point
would be to divorce Go’s versioning from the tools’ (nonexistent)
“versioning”.
--
Ticket URL: <https://trac.macports.org/ticket/41656#comment:10>
MacPorts <http://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list