mirror/autoconf
2
0
Fork 0
mirror of git://git.sv.gnu.org/autoconf synced 2025-02-17 14:01:27 +08:00
Code Issues Packages Projects Releases Wiki Activity

docs: tweak 'rm -f' limitations

Browse Source 
Based on http://debbugs.gnu.org/10819 and
http://austingroupbugs.net/view.php?id=542

* doc/autoconf.texi (Limitations of Usual Tools) <rm>: More
details on 'rm -f' without files.

Signed-off-by: Eric Blake <eblake@redhat.com>
This commit is contained in:
Eric Blake 2012-02-16 14:29:37 -07:00
parent e32b90e41f
commit 989c790c4f
1 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
doc/autoconf.texi
View File

@ -19225,10 +19225,12 @@ This problem no longer exists in Mac OS X 10.4.3.
@prindex @command{rm}
The @option{-f} and @option{-r} options are portable.
It is not portable to invoke @command{rm} without operands. For
example, on many systems @samp{rm -f -r} (with no other arguments)
silently succeeds without doing anything, but it fails with a diagnostic
on NetBSD 2.0.2.
It is not portable to invoke @command{rm} without options or operands.
On the other hand, Posix now requires @command{rm -f} to silently
succeed when there are no operands (useful for constructs like
@command{rm -rf $filelist} without first checking if @samp{$filelist}
was empty). But this was not always portable; at least NetBSD
@command{rm} built before 2008 would fail with a diagnostic.
A file might not be removed even if its parent directory is writable
and searchable. Many Posix hosts cannot remove a mount point, a named