Eric Blake <[EMAIL PROTECTED]> wrote:
> According to Andreas Schwab on 2/19/2008 2:32 PM:
> |> Under the influence of -L, does -xtype l work like -lname '*' in
> |> detecting just the broken symlinks?
> |
> | You don't use -L of course (it isn't supported by find 4.1 anyway).
> | Note that with -L
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Andreas Schwab on 2/19/2008 2:32 PM:
|> Under the influence of -L, does -xtype l work like -lname '*' in
|> detecting just the broken symlinks?
|
| You don't use -L of course (it isn't supported by find 4.1 anyway).
| Note that with -L yo
Eric Blake <[EMAIL PROTECTED]> writes:
> According to Andreas Schwab on 2/19/2008 8:37 AM:
> | Jim Meyering <[EMAIL PROTECTED]> writes:
> |
> |> +# Remove dangling symlinks in gnulib-populated directories.
> |> +# This depends on GNU find, and a relatively recent version at that.
> |> +# Ignore an
On Feb 19, 2008 8:12 PM, Eric Blake <[EMAIL PROTECTED]> wrote:
> The goal here is not to delete all symlinks, just symlinks that are
> broken. Under the influence of -L, does -xtype l work like -lname '*' in
> detecting just the broken symlinks?
For that you want "find . -depth -type l -xtype l -
Jim Meyering <[EMAIL PROTECTED]> writes:
> +# Remove dangling symlinks in gnulib-populated directories.
> +# This depends on GNU find, and a relatively recent version at that.
> +# Ignore any failure for now, since it's only to avoid the relatively
> +# unusual case in which a symlinked-to file in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Andreas Schwab on 2/19/2008 8:37 AM:
| Jim Meyering <[EMAIL PROTECTED]> writes:
|
|> +# Remove dangling symlinks in gnulib-populated directories.
|> +# This depends on GNU find, and a relatively recent version at that.
|> +# Ignore any fa
Hello,
* Eric Blake wrote on Tue, Feb 19, 2008 at 02:28:35PM CET:
> [adding bug-automake]
>
> According to Jim Meyering on 2/19/2008 4:33 AM:
> |> But I am, having seen it myself. It happens when you have a stale symlink
> |> from an older copy of gnulib, but which now points nowhere because the
Eric Blake <[EMAIL PROTECTED]> wrote:
> [adding bug-automake]
>
> According to Jim Meyering on 2/19/2008 4:33 AM:
> |> But I am, having seen it myself. It happens when you have a stale symlink
> |> from an older copy of gnulib, but which now points nowhere because the
> |> file was renamed in gnu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[adding bug-automake]
According to Jim Meyering on 2/19/2008 4:33 AM:
|> But I am, having seen it myself. It happens when you have a stale symlink
|> from an older copy of gnulib, but which now points nowhere because the
|> file was renamed in gnuli
