[Ns-developers] nsc download tooooooo slow!

[Sam Jansen]

This is the first mail to the list about this, but you're not the first to
mention this problem...
I was actually looking at this yesterday, and I did a clone locally to the
server hosting the repository. Even in that case it took almost 2 minutes,
which is a bit frustrating. Looking at the mercurial documentation, there
does not appear to be any way to clone only part of the history.
Unfortunately NSC has a history involving many stack versions which will be
hundreds of thousands of lines of code.

It might make more sense for ns-3 to default to downloading a tarball of an
NSC release rather than using mercurial to clone the NSC repository.
Personally I think this is fine because NSC tends to be fairly slow moving.
Right now it only downloads a tarball if the user does not have mercurial
installed.

For the time being, you'll have to be patient. ns-3 is currently going
through its release cycle so isn't about to change for a little while. But
we can consider revising this mechanism for future ns-3 release.

2008/9/19 Weng Gavin <gavinweng at gmail.com>

> Since it is using https and have a huge amount of changesets.......Could
> somebody simplify it?
>