Home page logo

nmap-dev logo Nmap Development mailing list archives

Re: [RFC][PATCH] NSE Version Numbering
From: David Fifield <david () bamsoftware com>
Date: Sat, 12 Feb 2011 14:29:46 -0800

On Tue, Dec 14, 2010 at 09:31:06AM -0500, Patrick Donnelly wrote:
Hi Djalal,
On Tue, Dec 14, 2010 at 9:10 AM, Djalal Harouni <tixxdz () gmail com> wrote:
The version numbering is very simple e.g: 0.01 (Lua number) this value
will be incremented if there are some new NSE features that will have
a direct impact on NSE scripts/libraries and will *modify* their
behaviour, or a change on the NSE *core* functionalities, anything
related to the NSE core. As an example modifying/adding nse_*.cc
interfaces must be documented in the luadoc files:
file nmap.luadoc:

I've given this some thought and my take is that version numbers
should probably be the revision number in the repository. So long as
Nmap remains on subversion, this makes sense and is automatic. It
should be trivial to make adding (updating) this field automatic in
the build process.

I was just thinking that this won't work when releases are built from
branches. Numbers are global across the repository so the number in, for
example, /nmap-releases/5.51 could be ahead of that in trunk even though
it might not have the same NSE updates as trunk.

David Fifield
Sent through the nmap-dev mailing list
Archived at http://seclists.org/nmap-dev/

  By Date           By Thread  

Current thread:
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]