lantz

That's too bad, and a bit surprising since Debian and Ubuntu were OK with it. As you know, relicensing is tricky. Unfortunately the hard part is getting approval from Stanford,...

@Enchufa2 Actually managed to get the approvals (in addition to my own) with help from folks at ONF and Stanford. Merged in #1141 Github now auto-detects it as a BSD...

Hmm, does this make sense? But I think for the mininet vm we still want the build dirs to be in the root dir, so maybe have a way of...

@ederlf Thanks, looking forward to it.

Great, thanks!

@juangascon @ederlf Can you confirm that this works on both 14.04 and 16.04? Of course, it would be nice if we tested all the ancillary installations supported by `install.sh`, but...

@cheriimoya 's comment is on point; this error is also not reproducible.

I'm not a huge fan of the warning message, but if we add the `--no-python-version-warning` option then `make install` fails with earlier versions of pip. Right now we sidestep this...

I don't think this fixes the issue, since you could just put a quote in the string. The way `cmd` works is it passes strings to the shell which executes...

Working with python 2 is important. If we break backward compatibility in a big way that would probably need to be in a 3.x version of mininet.