On Feb 12, 2010, at 4:44 AM, Arno Hautala <[email protected]> wrote:
On Fri, Feb 12, 2010 at 07:39, Taka Fukuda <[email protected]>
wrote:
Could someone give me advice on how to access the latest list?
When was the last time that you ran "port selfupdate" ?
I've been wondering this for a while. Could a selfupdate version file
be kept on a few mirrors? Then with a little checking code, MacPorts
could run a pre selfupdate check prior to any users "port" command.
Your port tree/version is out of date, you may want to run "port
selfupdate'".
Probably exit at that point and set a local file that determines the
ignore state of that question. This way, the next run is not
interfered with if they chose to not update for whatever reasons.
I know this leans on interactive, which MacPorts appears to avoid, but
with some thought, it could be a gentle reminder to be up to date.
MacPorts is one of the few softwares I keep up to date at all times,
ignoring my "if it ain't broke, don't fix it" mantra I apply to
desktop apps, and usually the entire Mamp stack.
Though I've been a lot more brave with Mamp since I started using
MacPorts. Other than a few misplaced files, directories, includes, and
sockets, it's all an amazingly smooth process.
I'll jinx myself, but until MacPorts I was never able to bump php on a
live server and have the only downtime amount to the time it takes
graceful to do it's thing. I do test locally first before hitting up
production though, not that brave :)
--
Scott
(Sent from a mobile device)
_______________________________________________
macports-users mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
