[MacPorts] #38697: mdmg says it's up-to-date when it isn't
MacPorts
noreply at macports.org
Sat Apr 6 11:49:42 PDT 2013
#38697: mdmg says it's up-to-date when it isn't
---------------------------+--------------------------------
Reporter: rogerdpack@… | Owner: macports-tickets@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: base | Version: 2.1.3
Resolution: | Keywords:
Port: |
---------------------------+--------------------------------
Changes (by ryandesign@…):
* component: ports => base
Old description:
> 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?
New description:
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?
--
Comment:
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.
--
Ticket URL: <https://trac.macports.org/ticket/38697#comment:2>
MacPorts <http://www.macports.org/>
Ports system for OS X
More information about the macports-tickets
mailing list