Bug 249367 - dns/knot2: delete port
Summary: dns/knot2: delete port
Status: Open
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-ports-bugs (Nobody)
Depends on: 249366
  Show dependency treegraph
Reported: 2020-09-16 10:44 UTC by Leo Vandewoestijne
Modified: 2020-11-03 12:00 UTC (History)
2 users (show)

See Also:
freebsd: maintainer-feedback+

delete knot2 (12.84 KB, patch)
2020-09-16 10:44 UTC, Leo Vandewoestijne
freebsd: maintainer-approval+
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
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 freebsd_committer 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.
Comment 3 Danilo G. Baio freebsd_committer 2020-11-02 14:44:33 UTC
There is a new 2.X version upstream:

What about update it and mark as deprecated and set an expiry date for two or three months?

Because it seems they will still be maintaining it for a while.
"Since then, it doesn't receive new features or enhancements anymore, but it receives all important fixes. It lacks the latest features, but it's more time-proven."
Comment 4 Kurt Jaeger freebsd_committer 2020-11-02 15:19:49 UTC
Like this ?

DEPRECATED=     Use knot3, it is functionally compatible with 2.9.x
Comment 5 Leo Vandewoestijne 2020-11-03 12:00:01 UTC
(In reply to Danilo G. Baio from comment #3)

> Because it seems they will still be maintaining it for a while.
I have to admit that I didn't comprehend that from the announcements, but understood the moment 2.9.7 was released.

I guess I best upgrade the dns/knot2 port AND use these two lines Kurt suggested.