|Summary:||dns/knot2: delete port|
|Product:||Ports & Packages||Reporter:||Leo Vandewoestijne <freebsd>|
|Component:||Individual Port(s)||Assignee:||freebsd-ports-bugs (Nobody) <ports-bugs>|
|Severity:||Affects Only Me||CC:||pi|
|Bug Depends on:||249366|
Description Leo Vandewoestijne 2020-09-16 10:44:20 UTC
Created attachment 218002 [details] delete knot2 After dns/knot2-lib is deleted the port dns/knot2 can also be removed.
Comment 1 Kurt Jaeger 2020-10-04 11:14:39 UTC
Is there any possibility that some knot2 config can not run under knot3 ? Should knot2 be kept at least for a while (mabye with DEPRECATED and EXPIRE) ?
Comment 2 Leo Vandewoestijne 2020-10-06 08:44:48 UTC
From my own experience I saw an obsolete option just generate a non-blocking warning at validation at startup. The page https://www.knot-dns.cz/docs/3.0/html/migration.html#upgrade-2-9-x-to-3-0-x states: "Knot DNS version 3.0.x is functionally compatible with 2.9.x.". So I don't think "cooling down" with DEPRECATED or EXPIRE is needed, but I wouldn't mind having that for a while. But the software will be unmaintained. What would be nice however, would be something like in Perl5, when you update say perl5-5.26 you automatically get perl5-5.32, but I don't know how and where that's managed.