mdmg says it's up-to-date when it isn't

[rogerdpack@…]

after running "port mdmg xxx" once, then rebuilding one of "xxx's" dependencies, then running "port mdmg xxx" a second time, it responded like this:

$ port mdmg rdp-projects
...
(it rebuilds mplayer-edl, which has changed)
--->  Staging mplayer-edl into destroot
...
--->  Creating disk image for rdp-projects-0
--->  Disk Image for rdp-projects-0 is up-to-date

and appears not to recreate the .dmg file, even though dependencies had changed so..I guess this is a bug?

[rogerdpack@…]

as a note, the dependency in this case reinstalled because of "Portfile changed since last build; discarding previous state." FWIW

[ryandesign (Ryan Carsten Schmidt)]

According to the code, the mtime of the disk image is compared to the mtime of the portfile. If the disk image is newer, it is considered to be up to date. Dependencies are not considered. This could be considered a bug. To work around it, you can manually delete the old disk image to allow MacPorts to create a new one.

[afb@…]

Also, there has been no reason to build disk images since Tiger. They were replaced with flat packages (port mpkg), for Leopard and beyond.