Re: Bug#115953: apt-get -d install <package> doesn't work as documented

[János Holányi <csani@lme.linux.hu>]

reopen 115953
thanks

Quoting Jason Gunthorpe <jgg@debian.org>:

> 
> On Wed, 17 Oct 2001, János Holányi wrote:
> 
> > I still find it a contradiction. Please re-read my report, the manpage
> and the
> > output.
> 
> I find the man page perfectly clear. The options are not commands, they
> are modifiers. So 'apt-get --download-only install foo' should be read
> as
> 'do "install foo" but modify it to do only the download step'

You are right, 'apt-get --download-only install foo' should be read as
'do "install foo" but modify it to do only the download step'.

However, the manpage excerpt should be read as-is:
'       --download-only
              Download  only;  package  files are only retrieved,
              not unpacked  or  installed.
'
Please pay attention also to 'not unpacked', if you still feel this issue is
perfect as it is now... Also 'package files __are__ (...) __retrieved__'
It still smells fishy for me...

The bottom line:

Please let me know how can I retrieve a set of dependency-conflict-free deb
files from the official debian archive - using 'standard' and existing Debian
tools -, without having to copy&paste the output of apt-get -d install <foo1>
... <fooN>, into an editor, build a file list and a wget command line to get all
those in one shot...
Why not be able to do that by wanting to use 'apt-get -d install <foo1> ...
<fooN>' (or better, as I suggested, by using a new command: apt-get deb <foo1>
... <fooN>)?
Please.
Pretty please...? :>

Thank you.

Csan

János Holányi
Hungarian Association of Linux Users
Email: csani@lme.linux.hu