Hi, On Sat, 2005-03-12 at 14:16 +0100, Michelle Konzack wrote: > > Are we talking about features being "good" or "bad"? Or about intended > > and documented behaviour? Consider someone that says, at the command > > line: "Get me a copy of this .deb into the current directory." (using > > "aptitude download <package>", as documented). Then, aptitude (at least, > > the command line version) shouldn't try to be intelligent and say: "No, > > this is bad!". > > No, because you download only via http or ftp.
In the "copy" case, the file is also put in the current directory. So this also derives from _your_ understanding of the definition of "download". > > If you don't want a copy of the respective package in the current > > directory, just don't call "aptitude download <package>". > > This is false, because a local file can not downloaded, because it > is already there. The same thing is with installation from CD. I'm not talking about installation. Maybe this is the reason for the misunderstanding. As I already wrote, the behaviour for the "install" case does not need change. > Local files can only be copied but not downloaded. I think, you > have a false understanding between "downloading" and "copying". I'm just interpreting the documented behaviour of the program. If not resolving the issue as suggested, then please at least change the documentation (man page). Is there any other good way of obtaining a .deb file (as referenced from /etc/apt/sources.list) to the current (or any other specified) directory? BTW: Why are you so resistant to the suggested change? Which harm would it do? (Are you calling "aptitude download <package>" for the "file" case if you _don't_ want the .deb file in the current directory?) bye, Roland -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
