fcopy exits with an error if file is not updated because its up2date

[Oliver Osburg]

* Holger Levsen <debian at layer-acht.org> [070411 17:07]:
> Hi,
> 
> fcopy exits with an error if a file is not updated because its up2date, I 
> believe that is a bug. Because everything _is_ ok.
> 
> So I used to always do "fcopy -i foo", which today I have changed to "fcopy 
> foo || true" - which at least will tell me in the logs that something is 
> wrong. But I would prefer not to get an exitcode!=0 from fcopy in the first 
> place. 
> 
> Opinions?
> 
Hi,

yes, I agree! I'd prefer that behaviour, too. I also think that the
present behaviour is a bug...

regards, Oliver

--
 *  Oliver Osburg    -     Software and System Architect  *
 *  email: osburg at osburg.org     phone: +49 179 50 76 784 *
 *  note: All above is my opinion unless said otherwise   *
 * One Unix to rule them all, One Resolver to find them,  *
 * One IP to bring them all and in the zone bind them.    *