[Bug 206941] devel/capstone: adding new port for devel/capstone4 and adapting devel/capstone

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206941

--- Comment #9 from oleksii.tsai at gmail.com ---
(In reply to Kurt Jaeger from comment #8)
I don't have any objections. The reason i went this way is I was thinking about
devel/capstone tracking latest stable version. devel/capstone4 is sort of an
exception (workaround) as it not stable yet, however, already in use. I guess
our options are:
1) devel/capstone tracks stable releases (v3 for now), devel/capstone4 becomes
essentially devel/capstone-devel

or

2) rename devel/capstone to devel/capstone3, keep devel/capstone4 and then keep
adding new ports for any new major version.

Option 1 is easier on porter's side, however, looking at capstone project they
actually have various development branches which drastically differ, so not
clear which one to track.

Option 2 provides more variety to users and some flexibility to port
maintainers in case there are some outdated ports that use (or will use)
capstone. And actually nothing stops having devel/capstone in this case too.

Option 2 seems better to me now.

-- 
You are receiving this mail because:
You are the assignee for the bug.