[Buildroot] [PATCH v2] nmap: add option to build/install "ncat"

Carlos Santos casantos at datacom.ind.br
Mon Oct 9 23:55:11 UTC 2017


> From: "Arnout Vandecappelle" <arnout at mind.be>
> To: "Carlos Santos" <casantos at datacom.ind.br>
> Cc: buildroot at buildroot.org, "Thomas Petazzoni" <thomas.petazzoni at free-electrons.com>, "Maxime Hadjinlian"
> <maxime.hadjinlian at gmail.com>, "Peter Korsgaard" <peter at korsgaard.com>, "Yann E. MORIN" <yann.morin.1998 at free.fr>
> Sent: Monday, October 9, 2017 7:10:55 PM
> Subject: Re: [Buildroot] [PATCH v2] nmap: add option to build/install "ncat"

> On 10-10-17 00:08, Arnout Vandecappelle wrote:
>> 2. No specific option, always install nmap + ncat if BR2_PACKAGE_NMAP is
>> selected. Note that this might create a problem if both nmap and netcat-openbsd
>> are selected, so there should probably be a dependency introduced and a check
>> that nc doesn't exist yet before creating the symlink.
> 
> Let me clarify that bit: in all the other options, the user makes a conscious
> decision to enable ncat (and therefore the nc symlink). With this option,
> however, the nc symlink will be created without the user being aware of it, so
> it could be that it is not what the user intended. This is only a problem if
> netcat-openbsd is also installed (since ncat is a strict superset of GNU and
> busybox nc).

That was one of the advantages of the virtual package "nc": it
would require the user to choose only one netcat variant at a time.

Anyway, I can make the link creation optional or create it only if
none of the competing netcat variants is selected.

-- 
Carlos Santos (Casantos) - DATACOM, P&D
“The greatest triumph that modern PR can offer is the transcendent 
success of having your words and actions judged by your reputation, 
rather than the other way about.” — Christopher Hitchens



More information about the buildroot mailing list