Changes between Initial Version and Version 1 of Ticket #55469


Ignore:
Timestamp:
Dec 5, 2017, 4:41:45 AM (7 years ago)
Author:
ryandesign (Ryan Carsten Schmidt)
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #55469 – Description

    initial v1  
    55This change causes some ports to fail to build, namely those that need access to the changes the portgroup is making. For example, the moreutils port does not have a configure phase, so it gets the value of `${configure.ldflags}` to set flags for the build phase.
    66
    7 Now that the portgroup no longer changes `configure.ldflags` until after the portfile has been executed, the portfile doesn't have access to the changed variable, so [attachment:moreutils-port::register_callback-main.log the build fails] because `-lsnowleopardfixes` isn't in the ldflags. It [attachment:moreutils-main.log succeeded before the change].
     7Now that the portgroup no longer changes `configure.ldflags` until after the portfile has been executed, the portfile doesn't have access to the changed variable, so [attachment:moreutils-port__register_callback-main.log the build fails] because `-lsnowleopardfixes` isn't in the ldflags. It [attachment:moreutils-main.log succeeded before the change].
    88
    99The moreutils port could adapt to this changed behavior by enclosing the `build.args-append` command inside a `pre-build {...}` block. But if the point of making the portgroup use `port::register_callback` was to avoid having to change portfiles, then it fails at that goal.