[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: next steps for inetutils?
From: |
Alfred M. Szmidt |
Subject: |
Re: next steps for inetutils? |
Date: |
Sun, 07 Feb 2021 04:47:37 -0500 |
I pushed out a stable release now. Let's see if we get more
testing than for the pre-releases; we can always release something
in the coming weeks/month to fix build/portability stuff. There
isn't a lot of testing on BSD, Solaris, AIX and other non-GNU
systems as far as I know.
I think Mats-Erik is a heavy BSD and Solaris user, but I don't know
anyone else that might be using it.
Thank you for the roll-out, Simon!
* arp tool
* nc (netcat) tool
I like these additions, but I am worried about compatibility against
the more prolific versions of those tools.
* fix all warnings with autoconf 2.71 - I didn't want to touch this
before 2.0 since we had succesful build reports, but there are plenty
of old m4 constructs that we should use gnulib tools for instead.
* use gitlog-to-changelog instead of manual ChangeLog entries
I'm sorta still against it -- since it would ruin my work flow of
being able to edit the ChangeLog file post-factum. But I am sure I
can be convinced without much work ... if someone else does the
work. :-)
* Enhance Man pages so they fully supersede NetKit and BSD man pages
Can you elaboraet a bit?
* generally use gnulib for portability more than we use today.
Yes, yes, yes, pelase.
* Mingw/cygwin support?
If it is not much work, why not ...
* Remove Kerberos V4 support? I'm not sure there are any usable
Kerberos V4 implementations around anymore, and it is is
single-DES-only so they are completely insecure anyway.
Sounds like a good idea.