[Ns-bugs] [Bug 307] pybindgen not fetchable via web proxy

[bugzilla-daemon@nsnam-www.ece.gatech.edu]

http://www.nsnam.org/bugzilla/show_bug.cgi?id=307





------- Comment #2 from tomh at tomh.org  2008-09-04 08:26 -------

> > I'm not sure whether this is a bzr problem (have Googled and found some people
> > asking about bzr's proxy support)
> 
> Try upgrading bzr, or setting the http_proxy environment variable.  Luckily in
> the release tarballs bzr will not be used, so this is a problem for ns-3
> developers only.

setting http_proxy has no effect.  Agree this is mainly a development problem. 
I didn't mark it as high priority; is more of an inconvenience, along the lines
of the thread Mathieu started yesterday.  However, I am able to get other
pieces through a proxy.

> 
> > but I think that, regardless, if this occurs,
> > a more prominent error should display at the end of ./waf configure that alerts
> > the user to the lack of Python support.
> 
> So you are saying that lack of Python support is more important than e.g. lack
> of Gtk support, so that it deserves an additional warning in the end?  Or do
> you think we should perhaps present a summary in the end of all optional
> features, saying if they are enabled or not?  If seen such summaries in some
> configure scripts in some projects before...
> 

I think it would be helpful to have an output showing optionally configured
pieces; e.g.

Configuration status of ns-3 optional components:
-------------------------------------------------
Python bindings:  enabled
nsc:  disabled
...

I think Mathieu's proposal will also help to clearly identify what was
successfully downloaded or not.


-- 
Configure bugmail: http://www.nsnam.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.