[MacPorts] #44091: In port interactive mode, pseudo-portnames corrupted after selfupdate

MacPorts noreply at macports.org
Mon Jun 23 02:49:08 PDT 2014


#44091: In port interactive mode, pseudo-portnames corrupted after selfupdate
------------------------+--------------------------------
  Reporter:  pjkim00@…  |      Owner:  macports-tickets@…
      Type:  defect     |     Status:  new
  Priority:  Normal     |  Milestone:
 Component:  base       |    Version:  2.3.0
Resolution:             |   Keywords:
      Port:             |
------------------------+--------------------------------

Comment (by jmr@…):

 Replying to [comment:1 ryandesign@…]:
 >  * it is unusual to run `selfupdate` in interactive mode. Running
 selfupdate might update MacPorts. If so, MacPorts files may have been
 replaced/updated/removed, but you are still running the old version, which
 is not what you want; you want to be running the new version after
 selfupdating.
 This isn’t a problem, if base is actually updated then it exits
 immediately afterward.

 I can repro this, but only with pseudo-portnames that evaluate to an empty
 list. Looks like ‘list $foo’ is becoming just ‘list’ when $foo is the
 empty string, and of course ‘port list’ is documented to list all the
 ports. But it works properly at first for some reason.

-- 
Ticket URL: <https://trac.macports.org/ticket/44091#comment:4>
MacPorts <http://www.macports.org/>
Ports system for OS X


More information about the macports-tickets mailing list