[Ns-developers] build system proposal

[Mathieu Lacage]

comments below,

On Tue, 2008-09-30 at 16:36 +0000, Tom Henderson wrote:

> ns-3-allinone/
>              download.py
>              install.py
> 
> After invoking download.py, it would look something like this:
> 
> ns-3-allinone/
>              ns-3-dev/
>              pybindgen-dev/
>              nsc-dev/
>              ns-3-dev-ref-traces/
>              download.py
>              install.py
> 
> At any time when invoked later, download.py will synchronize all
> repos, 
> or if passed an argument or set of arguments, will synchronize all of
> the 
> named repos only.  Note:  Craig has suggested that maybe a separate
> script called "sync.py" or something like that could be used to do the
> later synchronization, and not reuse "download.py".


I would support instead making download.py require a mandatory argument.

./download.py --> do nothing, print help output.
./download.py all --> download everything
./download.py nsc --> download nsc
./download.py nsc ns-3 --> download nsc and ns-3.

> To update ns-3-dev, a developer in the ns-3-dev directory may either:
> i) hg pull (as usual)
> ii) ../sync.py ns-3-dev  (same outcome as i)
> iii) ../sync.py in which case everything is synchronized

I would suggest again "../sync.py all" to avoid spurious unwanted
updates.

Mathieu