Ask Different is a question and answer site for power users of Apple hardware and software. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

The goal is to insulate a code base from potential problems with new port upgrades.

So maybe if a port upgrade outdated command can be amended not to use the freshest of the fresh ports, you can avoid tracking down errors in ports affecting your code.

As far as I see, port info port_name doesn't have any extra release date options:

$ port help info
Usage: info --category --categories --depends_fetch --depends_extract --depends_build --depends_lib
            --depends_run --depends --description --epoch --fullname --heading --homepage     --index --license --line
            --long_description --maintainer --maintainers --name --platform --platforms --portdir --pretty
            --replaced_by --revision --subports --variant --variants --version

I suppose the best alternative to this is to perform daily incremental upgrades. Then when something breaks, it's easier to rollback since likely only a few ports will change per day.

share|improve this question

migrated from Oct 9 '12 at 10:09

This question came from our site for system and network administrators.

You could potentially monitor the SVN repo that all the Portfiles are distributed in to determine when last each port was changed.

Take a look here:, and set up a local copy of the macports trunk. Once in a while go see what revision number (#####) was committed about a month ago, and svn upgrade -r #####

Make sure you remove the default macports source, though:

#rsync:// [default]

Clearly a different approach to where you were heading with the port command, but it would work.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.