Author Topic: avast-update suggestion  (Read 5346 times)

0 Members and 1 Guest are viewing this topic.

ache

  • Guest
avast-update suggestion
« on: October 29, 2008, 11:59:30 AM »
The wget commands in the avast-update script conflicted with my wgetrc settings. Adding --no-timestamp after each wget helped. I suggest to do this in the distributed package.

Offline zilog

  • Avast team
  • Advanced Poster
  • *
  • Posts: 957
  • or #f0; daa; add a,#a0; adc a,#40
Re: avast-update suggestion
« Reply #1 on: October 30, 2008, 03:30:03 PM »
The wget commands in the avast-update script conflicted with my wgetrc settings. Adding --no-timestamp after each wget helped. I suggest to do this in the distributed package.

well, when you changed the default behavior using .wgetrc, it's necessary to use such switch to get rid of the timestamping (which is non-standard). but, this might affect the 400vps.md5 only (because 400.vps changes its size, and different size overrides the timestamping-based bail-out).

i'm not sure whether older versions of wget supported this switch:

sinclair:~# wget -V
GNU Wget 1.9.1

Copyright (C) 2003 Free Software Foundation, Inc.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
GNU General Public License for more details.

Originally written by Hrvoje Niksic <hniksic@xemacs.org>.
sinclair:~# wget --no-timestamp
wget: unrecognized option `--no-timestamp'
Usage: wget [OPTION]... [URL]...

Try `wget --help' for more options.


... and yes, they didn't, so in the fact such switch would block the functionality there
... and that's why it's better to rely on the standard behavior.

regards,
pc
« Last Edit: October 30, 2008, 04:19:24 PM by zilog »
May's Law: Software efficiency halves every 18 months, compensating Moore's Law. (David May, INMOS)