#44700: Request: download-friendly installer package URLs -----------------------------+------------------------- Reporter: george@… | Owner: skarulkar@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: server/hosting | Version: Resolution: | Keywords: Port: | -----------------------------+------------------------- Comment (by ryandesign@…):
We are talking about the macports installer version, given a certain major level of MacOSX, correct? Is it not the first thing a user does after installation of macports is selfupdate? That means that macports will always be updated, no matter what.
Not only is `sudo port selfupdate` something we recommend users run frequently (and nag them to run if they haven't in the past two weeks), it's also done by the installer before it finishes. So it doesn't particularly matter if you just code your script to download and install MacPorts 2.3.1 for now and pretty much forget about it for a few years; even if we release new versions of MacPorts in that time, the MacPorts 2.3.1 installer will leave you with the current version of MacPorts. It is possible that in the distant future we may limit how far back `selfupdate` is able to update MacPorts; we've done that once before. If we do that again, you may have to update the version of MacPorts your script installs at that time.
If we are talking about the version of a certain port, no problem: Ports that I need to pin, I just tell puppet to ensure they are at a certain version.
I'm not familiar with puppet's capabilities, but note that MacPorts does not have a built-in capability for installing older versions of a port; it's currently a [wiki:howto/InstallingOlderPort manual process] and not one we intend users to need to perform on a regular basis. -- Ticket URL: <https://trac.macports.org/ticket/44700#comment:6> MacPorts <http://www.macports.org/> Ports system for OS X