Re: problem with wget -O
On Thu 28 Jan 2021 at 15:02:47 (-0500), Gene Heskett wrote:
> On Thursday 28 January 2021 11:10:48 Greg Wooledge wrote:
> > On Thu, Jan 28, 2021 at 10:06:25AM -0600, David Wright wrote:
> > > Perhaps file a bug against that page. It appears that they were
> > > using -O merely to avoid overwriting http://master.zip with the
> > > second instance of wget. The manpage expressly advises against doing
> > > that: "Use of -O is not intended to mean simply "use the name file
> > > instead of the one in the URL". They should just use mv after each
> > > wget to place the zip files where they want them.
> >
> > If -O is bad, then what are you supposed to use instead?
> >
> > If you need to "use mv after each wget", how do you know the name of
> > the file that wget used? And why can't you simply tell wget to use
> > the filename you *want* it to be written to? Why would you need to do
> > this weird two-step process?
>
> for a change, I am 100% with Greg W., in fact, if the file already
> exists, wget should assume a bad copy was previously obtained, and
> should then very cheerfully over write the existing file.
No thanks. (And it doesn't do that.) But then, I don't spend my
time "nuking" files on my system.
> […]
> But: I think I forgot to blow away the older build dir
> […]
> Until then, lets put this thread to rest. wget was fixed by blowing away
> my /home/me/.wgetrc
Sorry, "blowing away", not "nuking".
At first glance, it looked like a reasonable file to use with --config=,
on the right occasions.
Cheers,
David.
Reply to: