[MacPorts] #55241: base: MediaInfo: fails to upgrade in normal `port upgrade outdated` run

MacPorts noreply at macports.org
Sat Nov 4 15:11:22 UTC 2017


#55241: base: MediaInfo: fails to upgrade in normal `port upgrade outdated` run
------------------------+--------------------
  Reporter:  Ionic      |      Owner:
      Type:  defect     |     Status:  new
  Priority:  Normal     |  Milestone:
 Component:  base       |    Version:  2.4.99
Resolution:             |   Keywords:
      Port:  MediaInfo  |
------------------------+--------------------

Comment (by Ionic):

 Replying to [comment:8 ryandesign]:
 > We want port names to be handled case-insensitively. There have been
 numerous case-only renames of ports in the past and we want to continue to
 allow that to happen in the future if needed. `port upgrade outdated`
 should be fixed to handle this.

 I don't know which part is failing here. It seems that medialib doesn't
 have a directory matching its name and then there was the case-only
 rename.

 Activating the old version of `mediainfo` (incidentally lowercase),
 renaming the port's directory to `MediaInfo` and regenerating the
 PortIndex leads to the same symptom - `port outdated` lists the port, but
 `port upgrade outdated` doesn't see any upgradable ports.

 Base definitely isn't handling this well.

 Also, I've noticed that dependencies sometimes are case sensitive.
 `port:ZenLib` != `port:zenlib` - at least for trace mode. At least base
 tried building `ZenLib` before `MediaInfoLib` when the dependency was only
 written as `port:zenlib` in `MediaInfoLib`, so I figure only trace mode is
 not handling this very well, with other components being more resilient.

 Which reminds me, the dependency is also "faulty" in `MediaInfo` itself,
 so I'll fix it up as well.


 > If you meant to change the case of the port name, then fix the case of
 the directory to match. If you did not mean to change the case of the port
 name, put the port name back to the old case.

 As already pointed out, that's a bad idea IMHO, since in that case we'll
 just shift the problem to new installations that pulled in the `MediaInfo`
 name (and people who already upgraded to `MediaInfo` "manually").

--
Ticket URL: <https://trac.macports.org/ticket/55241#comment:9>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list