nmap: bump to 7.99

[smallprogram]

📦 Package Details

Maintainer: @nunojpg
_{(You can find this by checking the history of the package Makefile.)}

Description:
nmap: bump to 7.99

---

🧪 Run Testing Details

• OpenWrt Version: Openwrt Snapshot
• OpenWrt Target/Subtarget: X86/64
• OpenWrt Device: R2

---

✅ Formalities

• I have reviewed the CONTRIBUTING.md file for detailed contributing guidelines.

If your PR contains a patch:

• It can be applied using git am
• It has been refreshed to avoid offsets, fuzzes, etc., using

  make package/<your-package>/refresh V=s

• It is structured in a way that it is potentially upstreamable
  _{(e.g., subject line, commit description, etc.)
  We must try to upstream patches to reduce maintenance burden.}

[GeorgeSapkin]

I have asked you multiple times in the past to please read and follow the contributing guidelines:

• golang: bump to 1.25.6 #28378
• docker: bump to 29.2.0 #28452
• adguardhome: add enabled option #29261

Edit: and yet again you didn't tag the maintainer.

[GeorgeSapkin]

Why did you change all of these in a minor version bump?

[nunojpg]

You are removing ndiff? That needs to have an explanation in the commit, if some exists.

[smallprogram]

You are removing ndiff? That needs to have an explanation in the commit, if some exists.

When upgrading Nmap to version 7.99, retaining the existing ndiff configuration results in a compilation error, specifically:

can't open file '.../ndiff/setup.py': No such file or directory

The root cause is that Nmap version 7.99 has undergone a major overhaul of the build system for its Python-based tools (such as ndiff and Zenmap):

In Nmap 7.94, ndiff still relied on the traditional Python setup.py script for packaging and installation.

By Nmap 7.99, the project officially deprecated setup.py entirely, transitioning instead to modern Python packaging standards (utilizing pyproject.toml and wheel).

Consequently, simply updating the version number and hash was insufficient; I therefore removed the obsolete elements from the Makefile, and the build subsequently passed all compilation tests.

[nunojpg]

I think there could be a argument to remove ndiff if no one is interested in supporting it for a few years, but wouldn't trade a version bump for removing ndiff without a significant reason.

[smallprogram]

I think there could be a argument to remove ndiff if no one is interested in supporting it for a few years, but wouldn't trade a version bump for removing ndiff without a significant reason.

Alright, let's put this PR on hold for now. This is the only approach I have at the moment; perhaps you might have a better solution.

Thank you for taking the time to reply. I apologize for the intrusion.