Opened 11 months ago
Closed 7 months ago
#68907 closed defect (wontfix)
hyperscan: allow ragel-devel
Reported by: | barracuda156 | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.8.1 |
Keywords: | Cc: | ||
Port: | hyperscan |
Description
36-184% sudo port -v build hyperscan Warning: configured user/group macports does not exist, will build as root Portfile changed since last build; discarding previous state. ---> Computing dependencies for hyperscan.. Error: Can't install ragel because conflicting ports are active: ragel-devel
Change History (2)
comment:1 Changed 11 months ago by ryandesign (Ryan Carsten Schmidt)
comment:2 Changed 7 months ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → wontfix |
---|---|
Status: | new → closed |
I did try to build hyperscan @5.4.2 with ragel-devel @7.0.4 and it did succeed. However I'm inclined not to change anything here because hyperscan documentation states that it depends on ragel 6.9 exactly whereas for other dependencies they are listed with a minimum version rather than an exact version. It is possible that the parser generated by ragel 7.x is different from the one generated by ragel 6.x in a way that matters to hyperscan.
Note: See
TracTickets for help on using
tickets.
Last 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 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.