Date: Thu, 9 Mar 95 02:54:46 +0100 From: jmz@cabri.obs-besancon.fr (Jean-Marc Zucconi) To: asami@cs.berkeley.edu Cc: ports@FreeBSD.org Subject: Re: ncftp ftp://site/dir/foo.tar.gz Message-ID: <9503090154.AA23186@cabri.obs-besancon.fr> In-Reply-To: <199503082044.MAA16237@forgery.CS.Berkeley.EDU> (asami@cs.berkeley.edu)
next in thread | previous in thread | raw e-mail | index | archive | help
>>>>> "Satoshi" == Satoshi Asami/=?ISO-2022-JP?B?GyRCQHUbKEI=?= =?ISO-2022-JP?B?GyRCOCsbKEIgGyRCOC0bKEI=?= <asami@cs.berkeley.edu> writes: > * Ncftp has problems with wu-ftpd if you try to get a directory foo/ as > * foo.tar.gz. > Well, the question is: how easy is this to fix? Actually blindly > getting /path1/path2/dir.tar.gz is not a very good idea, as it will > include all the pathnames in the tar file. > Do you think we can change ncftp to issue a CWD command first? > Andrew, are you there? :) I think that we can easily change the code to use something like 'ncftp -C /path1/path2 ftpsite:dir.tar.gz' instead of 'ncftp ftpsite:/path1/path2/dir.tar.gz' but we may sometimes need partial paths in the tar file (eg. cd /path1 and then get path2/dir.tar.gz) for which I don't see a simple solution. (I have not read the code though :-)) > Satoshi > P.S. Another solution is to do a "(echo $dir; echo get $file) | ncftp > -N $site" sort of thing in bsd.port.mk, but I'm not sure if we > want to make it this complicated.... Yes, you can even complicate the command to use plain ftp! Jean-Marc. ~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~ Jean-Marc Zucconi | jmz@cabri.obs-besancon.fr Observatoire de Besancon | F 25010 Besancon cedex | PGP Key: finger jmz@cabri.obs-besancon.fr =========================================================================
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9503090154.AA23186>