[net-dns-users] sep() and is_sep()
rwfranks at acm.org
Wed May 28 14:28:20 UTC 2014
Calle makes a good point; and it was my fault entirely.
The 3rd party back-compatibility issue did not cross my mind when I did
Cleanest solution would be to reissue with warning removed. We can put it
back when 0.17 get consigned to oblivion in BACKPAN.
Messy workarounds always seem to find a way to bite someone, somewhere,
On 28 May 2014 13:16, Calle Dybedahl <calle at init.se> wrote:
> On 28 maj 2014, at 13:49, Willem Toorop <willem at nlnetlabs.nl> wrote:
> > What would you like us to do now? Re-release with the warning removed?
> > Now the damage has been done already, it might be just as easy for
> > modules using Net::DNS::SEC to adapt and re-release with an updated
> > dependency. What do you think?
> Given that it’s not that serious a problem (I’m guessing that not many
> people are interested in the is_sep() method, and of those who are even
> fewer are writing libraries for third-party use), I can’t think of a course
> of action that’s not more bother than it’s worth. So I’m fine with just
> leaving it at “Oops, let’s try not to do that again”.
> At a practical level, what I’ve done in DNSCheck is to change the code to
> use sep() instead of is_sep(), and monkey-patch a sep() method into
> Net::DNS::RR::DNSKEY if the Net::DNS::SEC version is 0.17 or lower. It’s
> not a pretty solution, but it works, so I thought I’d mention it here in
> case someone else is in a similar situation.
> Calle Dybedahl
> calle at init.se -*- +46 703 - 970 612
> net-dns-users mailing list
> net-dns-users at nlnetlabs.nl
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the net-dns-users