bug-inetutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

next steps for inetutils?


From: Simon Josefsson
Subject: next steps for inetutils?
Date: Fri, 05 Feb 2021 16:19:00 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux)

"Alfred M. Szmidt" <ams@gnu.org> writes:

> I'm ok with doing a release now.

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 wasn't able to update the NEWS section on savannah, maybe we don't use
that?  If not, I'll fix README-release.

Now is a good time to do some changes that I think we should do but was
pending the release, any thoughts on the following?

* arp tool

* nc (netcat) tool

* 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

* enhance man pages so they fully supersede NetKit and BSD man pages

* generally use gnulib for portability more than we use today.

  - gnulib has fts.c that we have a custom libls/ for

  - getaddrinfo/getnameinfo with IDN support to simplify IDN complexity

  - more system header files replacements

  - ruserok/wtmp stuff

* Mingw/cygwin support?

* 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.

Please add more stuff!  Or disagree.

/Simon

Attachment: signature.asc
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]