Re: upcoming tcpslice 1.8

[Denis Ovsienko <denis () ovsienko info>]

On Mon, 09 Sep 2024 15:13:49 -0400
Michael Richardson <mcr () sandelman ca> wrote:

> Denis Ovsienko <denis () ovsienko info> wrote:
>     > Let me suggest making tcpslice 1.8 release in 1-2 weeks to
>     > avoid yet another oversized change log section.  If anyone sees
>     > a good reason not to, please make your point before long.  
>
> Who are the users of tcpslice?
> Are there any heavy users that would like to identify themselves, and
> verify the releases?

My guess is that tcpslice does not have many users, but from the
occasional bug reports is seems some people still use it.  Many
distributions have a package for it, although many packages are badly
outdated.  Sometimes I notify one or another package maintainer about a
new version, but still in this department it is not uncommon to measure
the feedback loop in years.

I revived tcpslice in 2020 during a COVID lockdown with the intent to
convert some spare time to a few simple bug fixes.  In 2021 it turned
out to be the best guinea pig for the CI improvements (build matrix
etc): it uses libpcap and has a very low build time compared to
tcpdump, so in this department the feedback loop can be measured in
minutes, not hours.  Its purpose since then has been to provide a
testing ground for various improvements (e.g. handling of various
warnings/errors, man page formatting, posix_fadvise(), static builds,
git for releasetar etc) before they are ready to apply to libpcap and
tcpdump.

So, I am going to make the next release anytime soon.

-- 
    Denis Ovsienko
_______________________________________________
tcpdump-workers mailing list -- tcpdump-workers () lists tcpdump org
To unsubscribe send an email to tcpdump-workers-leave () lists tcpdump org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s