Changes between Initial Version and Version 1 of Ticket #68907, comment 1


Ignore:
Timestamp:
Dec 27, 2023, 9:11:58 PM (9 months ago)
Author:
ryandesign (Ryan Carsten Schmidt)
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #68907, comment 1

    initial v1  
    1 Last I checked, ragel-devel (version 7) was very different from ragel (version 6) and none of the ports I checked that depended on ragel worked with ragel-devel, so the conflict you're seeing is intentional. See the comment at the top of the [source:macports-ports/lang/ragel/Portfile ragel Portfile]. If you like, you can try changing the dependency in hyperscan to `path:bin/ragel:ragel` and see if hyperscan is still able to build. But if the developer of ragel does not fix ragel 7 to be more backward-compatible with ragel 6 we may have to rename ragel to ragel6 and rename ragel-devel to ragel7 and install them to separate locations so they don't conflict.
     1Last I checked (13 months ago when I created the ragel-devel port), ragel-devel (version 7) was very different from ragel (version 6) and none of the ports I checked that depended on ragel worked with ragel-devel, so the conflict you're seeing is intentional. See the comment at the top of the [source:macports-ports/lang/ragel/Portfile ragel Portfile]. If you like, you can try changing the dependency in hyperscan to `path:bin/ragel:ragel` and see if hyperscan is still able to build. But if the developer of ragel does not fix ragel 7 to be more backward-compatible with ragel 6 we may have to rename ragel to ragel6 and rename ragel-devel to ragel7 and install them to separate locations so they don't conflict.