mini-ndn

commit:d855f0776e26cf757d59b3e5a93d3a83b579d7d6 does not correctly implement the feature described above.

The procedure in that commit is:

1. clone Mininet git-HEAD
2. move Mininet code into the same directory as mini-ndn
3. install Mininet together with mini-ndn

The feature description specifies Mininet as a dependency, which means:

• A user should be able to install Mininet before mini-ndn, not at the same time.
• Mininet code should not be moved into the same directory as mini-ndn. (sub-directory, such as git-submodule, is fine)

Reference: https://github.com/yoursunny/mnndn, an emulator similar to mini-ndn that I used in a recent paper, which fulfills the above requirements.

So should I make it like your example (i.e. running by specifying PYTHONPATH) or provide something to do a system install?

Answer to note-2:

mini-ndn MAY do system install.

I didn't write system install script in mnndn because I don't need it.

I suggest providing a script that performs the following actions:

• -m: install Mininet and its dependencies
• -f: install NFD forwarder
• -r: install NLSR routing
• -t: install ndn-tools
• -i: install mini-ndn

Actions other than -i downloads and installs the package, but the user may as well install the package manually and not use the script action.

The -i action installs mini-ndn itself to the system.

For NFD, NLSR, and ndn-tools should I use the Ubuntu binaries?
If so, don't you think it will be better to let users install these dependencies themselves since they may be using other Linux distros?

Answer to note-4:

No, the script should compile them from source code, like what Mininet does for OpenFlow.