New version release with working installation script

Could we have a new release of mininet including the commit c3ba039 ?

Otherwise, we have to either tag explicitly the commit hash (or the master branch) or cherry pick the commit to get a working installation script

For those that need it now, I've forked the repo and created a release including the cherrypicked c3ba039 commit.

Is this necessary since #1100 was merged on February 23rd?

Generally the master branch is intended to be usable, but probably you are right that we should do a 2.3.1.

It is necessary to fix mininet version if I want to be certain of the behavior of my library that runs on top of mininet.

Otherwise, depending on the time of installation of the other library, I will have a different behavior.

And, it is cleaner to fix it with a real tag than with a commit hash.

I think this issue can be closed, as it was fixed in #1124 with tag 2.3.1b1 (aa0176f).

Thanks.

Closed by #1124.

Navigation Menu