[Ns-developers] gsoc wrapup

[Tom Henderson]

Mathieu Lacage wrote:
> hi florian,
> 
> On Sun, 2008-08-17 at 12:34 +0200, Florian Westphal wrote:
>> Mathieu Lacage <mathieu.lacage at sophia.inria.fr> wrote:
>> [..]
>>> Based on the information I have right now, it looks like florian's stuff
>>> is on track to be merged pretty soon after a couple of final reviews.
>> This would be great, please poke me via mail or irc if there should be
>> showstoppers, i'd really like to see it merged and will be happy to
>> help.
> 
> I did a final review of the code and sent you a couple of comments
> privately by email. Modulo a couple of very minor details, the code
> looks good for merging to me so, feel free to try to push to ns-3-dev
> when you are ready.

It would be nice to try to resolve (or log into the tracker) the issues 
quickly if possible so that it could be merged next week.  Raj, can you 
please review as well?

> 
> My plans for next week are to:
> 1) add waf support to nsc
> 2) allow you to enable or disable individual network stacks for the
> build: building them all is killing me on my 32bit box.
> 3) add support to the build system to download either a mercurial nsc
> repo or a nsc tarball depending on whether we are in release mode or not

these would be very helpful

> 
> Right now, downloading all of nsc is a bit bottleneck for me, whenever I
> do a new clone (and I do a lot of them everyday). So, there are 2
> options: either split nsc in multiple repos I can download separately
> based on which stacks are enabled and/or try to share the same nsc
> download among multiple ns-3-dev clones. I am not sure what the right
> solution is but this is really painful for me so, I will try to think
> about it some more.
> 

Something like

./waf configure --with-nsc=path

would be useful, IMO.  If we do that, it seems like we may need to check 
whether nsc version is up to date enough.

Also, do the regression and unit test suites need a flag to remember 
whether nsc has been enabled?

Regarding the merge of code like this, where someone has been working on 
a project for many months with a long change history, should we be 
merging repos with full change history or just producing a final patch 
that is merged to ns-3-dev?  Is it author's discretion whether or not to 
keep forever the private change history?

Tom