[Ns-developers] build stuff and downloading external deps

Tom Henderson tomh at tomh.org
Thu Sep 4 08:46:53 PDT 2008


>-----Original Message-----
>From: Mathieu Lacage [mailto:mathieu.lacage at sophia.inria.fr]
>Sent: Thursday, September 4, 2008 07:36 AM
>To: 'Tom Henderson'
>Cc: 'ns-developers'
>Subject: Re: [Ns-developers] build stuff and downloading external deps
>
>
>On Thu, 2008-09-04 at 15:08 +0000, Tom Henderson wrote:
>
>> First, to clarify, this is mainly about people working from ns-3-dev,
>> not from our releases.
>
>No. I would like to make that script handle releases too. Unless, of
>course, you are willing to generate the gigantic ns3-allinone tarball.

I think that we should generate an allinone tarball for each release, even if we also generate a smaller release that fetches components.  allinone has proven to be a very popular and convenient package for ns-2.

>
>
>> So, I don't see much extra advantage of having a separately invoked
>> download.py script to run if the above options work.
>
>The issue is that our build system is growing increasingly complex and a
>lot of functionality needs to be duplicated in a couple of locations. I
>would like to avoid that.
>

OK, I understand; I was just giving you my user perspective.  If the download pieces are broken apart from the configuration pieces, I would probably write my own wrapper script to do both.

Tom





More information about the Ns-developers mailing list