Is my MacPorts really sync-ing?

[Mark Hattam]

"selfupdate" is the command shown in the Wiki
http://trac.macosforge.org/projects/macports/wiki/UsingMacPortsQuickStart

and the text there says it's for grabbing the latest PortFiles.

i thought that the number after the underscore on the end of the port 
name showed the version of the Portfile ... so even if the version of 
the software hadn't changed, a change in the Portfile and perhaps 
important things about the way it's set up and installed were 
reflected by a incrementing number, and these were shown up by port 
outdated.

For instance
   freetype @2.3.4_0
   freetype @2.3.4_1
   freetype @2.3.5_0 (active)

So are portfile changes no longer reflected in this way? Or is there 
a different port command to show them up?


Mark

--

At 19:05 -0500 5/7/07, Ryan Schmidt wrote:
>On Jul 5, 2007, at 17:53, Mark Hattam wrote:
>
>>In that case it's changed what it reports with the -d ...  I've 
>>always used that because that what  the documentation says (or at 
>>least said) to do.
>
>-d means debug i.e. print more info.
>
>>It used to report the delta, ie the new, the changed and the 
>>deleted files. Now it seems to report everything.
>>I was wondering partly because of the several Apache2 Portfile 
>>changes I've seen go through on the "Commit Log" list, but haven't 
>>apparently been caught by the sudo port -d selfupdate, as the sudo 
>>port outdated hasn't brought up any results for Apache2
>
>selfupdate is only for updating MacPorts base infrastructure.
>
>port outdated will only show ports that are outdated. A portfile can 
>be updated without requiring users to reinstall the software. You 
>can look in Subversion and see the log of everything that has been 
>done to a portfile:
>
>http://trac.macosforge.org/projects/macports/log/trunk/dports/www/apache2
>
>You can see that in the latest change in June neither the version 
>nor the revision was updated, hence "port outdated" won't show it. 
>In this particular case, it might have been better had jberry also 
>incremented the port revision so that everyone would receive this 
>change. In other cases, that's not necessary.