[Nfd-dev] ndncat/putchunks: ndn-cxx or NFD tools?

[Junxiao Shi]

Hi Alex

Please create ndn-tools repository, and also Redmine project (as a
subproject of NFD).

I suggest we keep the current repositories (ndn-cxx, NFD, ndn-tlv-ping) for
v0.3, and change to the new set (ndn-cxx, NFD, ndn-tools) since v0.4.

Yours, Junxiao

On Mon, Jan 19, 2015 at 10:21 PM, Alex Afanasyev <
alexander.afanasyev at ucla.edu> wrote:

>
> On Jan 5, 2015, at 2:26 PM, Junxiao Shi <shijunxiao at email.arizona.edu>
> wrote:
>
> Hi Steve
>
> I'll begin with the third question.
>
> My observation and opinion is: a tool shall be bundled with ndn-cxx if it
> can be used without installing NFD.
> The two tools bundled with ndn-cxx are:
>
>    - ndnsec: controls the KeyChain
>    - tlvdump: parses the packet format
>
> They both don't require NFD.
>
>
> I recognize that there are certain tools which are not closely related to
> NFD, but are useful in most places where NFD is installed.
> They include:
>
>    - peek and poke
>    - catchunks and putchunks
>    - ping and pingserver
>
> I suggest creating a separate "ndn-tools" repository which contains all
> these tools.
> Operator still installs from three repositories, ndn-cxx, NFD, ndn-tools
> (formerly ndn-tlv-ping), so this change doesn't increase the difficulty of
> deployment.
>
>
> Having a separate `ndn-tools` repository seem to me to be a reasonable
> solution.  We just need to clearly describe on ndn-cxx and NFD pages that
> additional tools can/should be installed from a different repo.
>
> —
> Alex
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20150130/2a39ba49/attachment.html>