Changes between Initial Version and Version 1 of Ticket #66690, comment 7
- Timestamp:
- Feb 3, 2023, 11:15:43 AM (22 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #66690, comment 7
initial v1 1 1 I see the same issue with MacPorts 2.8.1 on both {{{arm64}}} and {{{x86_64}}}. 2 2 3 The problem with the latest MacPorts version is that the {{{worksrcpath}}} specified by the Portfile is created as an actual directory, not a symlink to the unta med source contents created by the {{{extract}}} phase. This will be a problem with any port that specifies {{{worksrcpath}}}—I cannot recall why I did this for {{{cabal}}} but I believe that there was a good reason. See below.3 The problem with the latest MacPorts version is that the {{{worksrcpath}}} specified by the Portfile is created as an actual directory, not a symlink to the untarred source contents created by the {{{extract}}} phase. This will be a problem with any port that specifies {{{worksrcpath}}}—I cannot recall why I did this for {{{cabal}}} but I believe that there was a good reason. See below. 4 4 5 5 This looks like a MacPorts bug to me. I'll issue a ticket.