[MacPorts] #15572: readline 5.2.012 fails to install (no such file or directory)

[MacPorts]

#15572: readline 5.2.012 fails to install (no such file or directory)
--------------------------------------+-------------------------------------
  Reporter:  silverdemon at sitosis.com  |       Owner:  macports-tickets at lists.macosforge.org
      Type:  defect                   |      Status:  new                                  
  Priority:  Normal                   |   Milestone:  Port Bugs                            
 Component:  ports                    |     Version:  1.6.0                                
Resolution:                           |    Keywords:                                       
--------------------------------------+-------------------------------------
Changes (by ryandesign at macports.org):

 * cc: jkh at apple.com (added)
  * milestone:  => Port Bugs

Comment:

 Yes, `-d` implies `-v`. `-v` does not imply `-d`. `-d` is a superset of
 `-v`. `-d` includes all information from `-v` and then some. `-v` is
 "verbose" and `-d` is "debug" (which is more verbose).

 All the output you got following "Removing build directory for readline"
 is expected -- you must have been in the build directory, and then
 MacPorts deleted the build directory, and then it didn't know how to put
 your shell back into that directory when it was done. No harm should come
 of these error messages. The port was installed properly. The messages
 would not have appeared had you run the port command from a directory that
 still existed when the port command finished.

 As to the actual problem of share/info/dir not existing, that's curious.
 I've never had this problem installing readline on several machines with
 several OS versions over the years. And the directive to remove that item
 has been in the portfile since r7643, which was committed almost four
 years ago (although the log message for that revision does not explain why
 it is being deleted; Cc'ing the committer of that revision for
 clarification). It looks like you're on a PowerPC with Mac OS X 10.5.3...
 That's one configuration I haven't used yet. What version of Xcode and
 MacPorts do you have?

 We could certainly modify the portfile to only delete the item if it
 exists. But before we do that it might be nice to understand why it has
 existed for everyone else installing the port over the past four years but
 not for you! :-)

-- 
Ticket URL: <http://trac.macports.org/ticket/15572#comment:2>
MacPorts <http://www.macports.org/>
Ports system for Mac OS