Bug 489

Summary:	ns-3-allinone inflexible WRT trace file location
Product:	ns-3	Reporter:	Craig Dowell <craigdo>
Component:	build system	Assignee:	ns-bugs <ns-bugs>
Status:	RESOLVED FIXED
Severity:	normal	CC:	gjcarneiro
Priority:	P1
Version:	pre-release
Hardware:	All
OS:	All
Attachments:	Patch to make regression trace files specification possible

Description Craig Dowell 2009-02-05 12:17:09 UTC

Created attachment 372 [details]
Patch to make regression trace files specification possible

As it stands allinone is very inflexible about how you can specify a regression trace file.  This makes life difficult for automated testing.

For example, if you have a repository craigdo/ns-3-tap, download.py tries to fetch http://code.nsnam.org/ns-3-tap-ref-traces.  This is not desirable.

Often, you want to make changes to some code and make sure that the standard reference traces are not affected.  In this case you would want to fetch ns-3-dev-ref-traces when your BRANCH is craigdo/ns-3-tap.

There needs to be a -r option in download.py to go along with the -n option, which defaults to all the right things -- for example, using ns-3-dev-ref-traces independent of your BRANCH as above.

Patch attached.

Comment 1 Gustavo J. A. M. Carneiro 2009-02-10 06:15:30 UTC

Sorry I did not realize there was a patch included in the bug report earlier;  I am used to GNOME's bugzilla, which does not allow new bug report with included patch in one step, and which shows a 'patch' icon in the bug list for bugs with patches attached.

I've pushed the patch.  I think more work is needed; it's starting to be about time to move to a single .config file for all state saving, using Python's ConfigParser module perhaps, instead of several tiny files.  But I have not had time to do it yet.