[perl #17487] ncftp only handles http
[EMAIL PROTECTED] - Tue Sep 07 06:28:44 2004]: I disagree with the final thought there. My machine did have a copy of wget on it so that wasn't the problem in my case (though it would be for a stock install of the current version of Mac OS X). Since it does present a problem for certain configurations, I would recommend requiring at least one FTP site be chosen. At very least, it could have given a warning. Requiring an FTP site is a coarse solution likely to just lead to a new set of complaints that CPAN.pm requires an FTP mirror. No, that's not the way. You mention that you have wget. CPAN.pm triest wget last after trying ncftp*. As its the most capable of all the options available it should be tried first. Then lynx. Then finally ncftp*. A patch for this is attached. CPAN.pm could check if the proto is HTTP and not try ncftp* but as they will be the last thing tried I think its more useful to try them than not. Who knows, maybe ncftpget will handle http urls in the future? CPAN.pm.patch Description: Binary data
Re: [perl #17487] ncftp only handles http
On Mon, Jul 11, 2005 at 11:19:06PM -0700, Michael G Schwern via RT wrote: CPAN.pm could check if the proto is HTTP and not try ncftp* but as they will be the last thing tried I think its more useful to try them than not. Who knows, maybe ncftpget will handle http urls in the future? Also there's only so much effort I want to put into this as CPANPLUS already gets it right. -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern Reality is that which, when you stop believing in it, doesn't go away. -- Phillip K. Dick
Re: [perl #17487] ncftp only handles http
On 7/12/05, Michael G Schwern via RT [EMAIL PROTECTED] wrote: You mention that you have wget. CPAN.pm triest wget last after trying ncftp*. As its the most capable of all the options available it should be tried first. Then lynx. Then finally ncftp*. A patch for this is attached. Can you include curl in it ? At the beginning or something ? It's extremely capable and has excellent error reporting.
Re: [perl #17487] ncftp only handles http
On Tue, Jul 12, 2005 at 12:00:02PM +0200, Rafael Garcia-Suarez wrote: On 7/12/05, Michael G Schwern via RT [EMAIL PROTECTED] wrote: You mention that you have wget. CPAN.pm triest wget last after trying ncftp*. As its the most capable of all the options available it should be tried first. Then lynx. Then finally ncftp*. A patch for this is attached. Can you include curl in it ? At the beginning or something ? It's extremely capable and has excellent error reporting. Since curl is included by default on Mac OS X and wget and lynx is not, I'd like to see curl a little farther up the list as well. Steve Peters [EMAIL PROTECTED]
Re: [perl #17487] ncftp only handles http
On Tue, Jul 12, 2005 at 05:09:15AM -0500, Steve Peters wrote: On Tue, Jul 12, 2005 at 12:00:02PM +0200, Rafael Garcia-Suarez wrote: On 7/12/05, Michael G Schwern via RT [EMAIL PROTECTED] wrote: You mention that you have wget. CPAN.pm triest wget last after trying ncftp*. As its the most capable of all the options available it should be tried first. Then lynx. Then finally ncftp*. A patch for this is attached. Can you include curl in it ? At the beginning or something ? It's extremely capable and has excellent error reporting. Since curl is included by default on Mac OS X and wget and lynx is not, I'd like to see curl a little farther up the list as well. Sure, but this involves new code. As the code for handling different download methods has more spagetti than an Italian resturaunt I'd like to finish this bug up and tackle curl as a separate bug. -- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern Reality is that which, when you stop believing in it, doesn't go away. -- Phillip K. Dick
Re: [perl #17487] ncftp only handles http
Michael G Schwern via RT wrote: [EMAIL PROTECTED] - Tue Sep 07 06:28:44 2004]: I disagree with the final thought there. My machine did have a copy of wget on it so that wasn't the problem in my case (though it would be for a stock install of the current version of Mac OS X). Since it does present a problem for certain configurations, I would recommend requiring at least one FTP site be chosen. At very least, it could have given a warning. Requiring an FTP site is a coarse solution likely to just lead to a new set of complaints that CPAN.pm requires an FTP mirror. No, that's not the way. You mention that you have wget. CPAN.pm triest wget last after trying ncftp*. As its the most capable of all the options available it should be tried first. Then lynx. Then finally ncftp*. A patch for this is attached. Thanks. Applied as change 25124. Radan Computational Ltd. The information contained in this message and any files transmitted with it are confidential and intended for the addressee(s) only. If you have received this message in error or there are any problems, please notify the sender immediately. The unauthorized use, disclosure, copying or alteration of this message is strictly forbidden. Note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Radan Computational Ltd. The recipient(s) of this message should check it and any attached files for viruses: Radan Computational will accept no liability for any damage caused by any virus transmitted by this email.
