[MacPorts] #70539: base: failure for building some ports (depending on conditions) when Macports is installed at deeper directory hierarchy with "--prefix" option

[MacPorts]

#70539: base: failure for building some ports (depending on conditions) when
Macports is installed at deeper directory hierarchy with  "--prefix"
option
----------------------------+--------------------
  Reporter:  nanigashi-uji  |      Owner:  (none)
      Type:  defect         |     Status:  new
  Priority:  Normal         |  Milestone:
 Component:  base           |    Version:  2.10.0
Resolution:                 |   Keywords:
      Port:                 |
----------------------------+--------------------

Comment (by ballapete):

 I installed MacPorts 2.10.5 from source with the patch. The path is now 33
 characters shorted, has "only" 140 characters. This is not sufficient for
 regular use of sockets. Additional 40 or 50 characters less would make the
 system practical. The component "_macports_release_tarballs_ports" (I am
 rsync'ing with nue.de.rsync.macports.org) is, in French, « une quantité
 négligeable ». I.e., could get lost. So that

 `/opt/local/var/macports/build/nue.de.rsync.macports.org_macports_release_tarballs_ports_textproc_libxml2`

 would become

 `/opt/local/var/macports/build/nue.de.rsync.macports.org_textproc_libxml2`
 or `/opt/local/var/macports/build/nue.de.rsync.macports.org-
 textproc_libxml2` (to better distinguish, or maybe = instead of -?).

 ≈70 characters – I do not need more, not even on Christmas.

 And it would *not* fail to display that this port comes from a local
 repository. Before the change they were built in
 `/opt/local/var/macports/build/_Volumes_BSD-Linux_MacPorts-
 distfiles_ports_p5-...`. ≈70 characters again, because I could leave out
 some designators, concentrating on Perl only.

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