[prev in list] [next in list] [prev in thread] [next in thread] 

List:       busybox
Subject:    Re: cp -va is not verbose when copying symlinks
From:       Denys Vlasenko <vda.linux () googlemail ! com>
Date:       2016-07-14 18:59:27
Message-ID: CAK1hOcP9hZeryhksd2sd6gHSDOo+kRYrbz-=ndPcffo7fff44w () mail ! gmail ! com
[Download RAW message or body]

Fixed in git, thanks!

On Mon, Jun 6, 2016 at 5:31 PM, Tony Kelman <tony@kelman.net> wrote:
> When I run the following with GNU coreutils (8.21 on Ubuntu 14.04 to
> be specific) I get this output:
>
> tkelman@nanosoldier4:/tmp$ touch afile
> tkelman@nanosoldier4:/tmp$ ln -s afile alink
> tkelman@nanosoldier4:/tmp$ export LC_ALL=C # ubuntu defaults to unicode
> quotes otherwise
> tkelman@nanosoldier4:/tmp$ cp -va afile bfile
> 'afile' -> 'bfile'
> tkelman@nanosoldier4:/tmp$ cp -va alink blink
> 'alink' -> 'blink'
>
> However with busybox (v1.24.2 in a docker container of Alpine Linux,
> which as far as I can tell is built with ENABLE_FEATURE_CP_LONG_OPTIONS)
> I get the expected output from cp -va on files, but not symbolic links:
>
> /tmp # touch afile
> /tmp # ln -s afile alink
> /tmp # cp -va afile bfile
> 'afile' -> 'bfile'
> /tmp # cp -va alink blink
> /tmp # busybox --help
> BusyBox v1.24.2 (2016-05-31 09:35:34 GMT) multi-call binary.
> BusyBox is copyrighted by many authors between 1998-2015.
> Licensed under GPLv2. See source distribution for detailed
> copyright notices.
>
> Is this a bug? Should the symbolic link code paths of cp be honoring
> FILEUTILS_VERBOSE?
>
> Thanks,
> Tony
>
>
> _______________________________________________
> busybox mailing list
> busybox@busybox.net
> http://lists.busybox.net/mailman/listinfo/busybox
_______________________________________________
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
[prev in list] [next in list] [prev in thread] [next in thread]