Fetch file -- use axel or prozilla instead of curl
I find file fetch is fairly slow esp. for sites like sf.net. port always chooses mirror easynews which is slow for me and prone of timeout. I checked /usr/local/share/darwinports/Tcl/port1.0/portfetch.tcl (I use /usr/local instead of /opt/local) and find file fetch uses curl. Since I installed and tested axel, I find it's fairly good, about as fast as prozilla (I have experience of using Gentoo which uses prozilla). My question is how to hack portfetch.tcl to use axel instead. Sure simply change curl to axel does not work. Wish someone can help me. Thanks.
I find it highly unlikely that any speed problems are curl's fault. It's hard to write a slow HTTP downloader ;) Perhaps you should try editing /opt/local/share/darwinports/resources/ port1.0/fetch/mirror_sites.tcl and reordering the mirror list? On Jan 31, 2007, at 11:18 AM, CHENG Gao wrote:
I find file fetch is fairly slow esp. for sites like sf.net. port always chooses mirror easynews which is slow for me and prone of timeout. I checked /usr/local/share/darwinports/Tcl/port1.0/portfetch.tcl (I use /usr/local instead of /opt/local) and find file fetch uses curl. Since I installed and tested axel, I find it's fairly good, about as fast as prozilla (I have experience of using Gentoo which uses prozilla).
My question is how to hack portfetch.tcl to use axel instead. Sure simply change curl to axel does not work.
Wish someone can help me. Thanks.
-- Kevin Ballard http://kevin.sb.org eridius@macports.org http://www.tildesoft.com
*On Wed, 31 Jan 2007 11:37:48 -0500 * Kevin Ballard <eridius@macports.org> climbed out of the dark hell and cried out:
I find it highly unlikely that any speed problems are curl's fault. It's hard to write a slow HTTP downloader ;)
Perhaps you should try editing /opt/local/share/darwinports/resources/ port1.0/fetch/mirror_sites.tcl and reordering the mirror list?
Thanks for the info. I'll try to reorder that. But anyway tools like axel/prozilla/aget should be faster than curl. Why not allow them as options? Maybe some setting in conf file, like fetchprogram axel or aget or prozilla? I dont know nothing about Tcl so I have no idea how to hack it. I found a page describing how to use wget instead, but seems portfetch.tcl has evolved, and simply change "eval curl" to "system wget/axel ..." wont work anymore. Anyway I can accept the situation. The worst solution for me is to use axel to get tarballs and put them in corresponding dirs under distfiles.
On Jan 31, 2007, at 11:37 AM, Kevin Ballard wrote:
I find it highly unlikely that any speed problems are curl's fault. It's hard to write a slow HTTP downloader ;)
Perhaps you should try editing /opt/local/share/darwinports/ resources/port1.0/fetch/mirror_sites.tcl and reordering the mirror list?
Or just wait for the impending macports 1.4 release which uses new sourceforge mirroring. -- Daniel J. Luke +========================================================+ | *---------------- dluke@geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+
*On Wed, 31 Jan 2007 11:56:43 -0500 * "Daniel J. Luke" <dluke@geeklair.net> climbed out of the dark hell and cried out:
On Jan 31, 2007, at 11:37 AM, Kevin Ballard wrote:
I find it highly unlikely that any speed problems are curl's fault. It's hard to write a slow HTTP downloader ;)
Perhaps you should try editing /opt/local/share/darwinports/ resources/port1.0/fetch/mirror_sites.tcl and reordering the mirror list?
Or just wait for the impending macports 1.4 release which uses new sourceforge mirroring.
I tried 1.4 (svn) and it has problem with pext_lib. I reported this and got no confirmation and replies.
On Jan 31, 2007, at 12:03 PM, CHENG Gao wrote:
Or just wait for the impending macports 1.4 release which uses new sourceforge mirroring.
I tried 1.4 (svn) and it has problem with pext_lib. I reported this and got no confirmation and replies.
The svn version is the development version, and if you're using it, you're expected to be able to fix problems yourself. If you wait for 1.4 to be released (so you get it when you do port selfupdate) you shouldn't have problems (and if you do, there will probably be people interested in helping it get fixed). -- Daniel J. Luke +========================================================+ | *---------------- dluke@geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+
*On Wed, 31 Jan 2007 12:19:17 -0500 * "Daniel J. Luke" <dluke@geeklair.net> climbed out of the dark hell and cried out:
On Jan 31, 2007, at 12:03 PM, CHENG Gao wrote:
Or just wait for the impending macports 1.4 release which uses new sourceforge mirroring.
I tried 1.4 (svn) and it has problem with pext_lib. I reported this and got no confirmation and replies.
The svn version is the development version, and if you're using it, you're expected to be able to fix problems yourself.
If you wait for 1.4 to be released (so you get it when you do port selfupdate) you shouldn't have problems (and if you do, there will probably be people interested in helping it get fixed).
Yes I know there may be problems with svn code. It doesn't matter. If it works, use it. If not, fall back to stable version. Now I decide to wait. :-p
participants (3)
-
CHENG Gao
-
Daniel J. Luke
-
Kevin Ballard