[bug #20970] Trailing slash on directory arguments breaks -name

Follow-up Comment #9, bug #20970 (project findutils): Also applied this patch to 4.2.x. ___ Reply to this item at: ___ Message sent via/by Savannah h

[bug #20970] Trailing slash on directory arguments breaks -name

Update of bug #20970 (project findutils): Open/Closed:Open => Closed Fixed Release:None => 4.3.11 ___ Reply to this item at:

[bug #20970] Trailing slash on directory arguments breaks -name

Update of bug #20970 (project findutils): Status: Confirmed => Fixed Assigned to: ericb => jay ___ Reply to this item at:

[bug #20970] Trailing slash on directory arguments breaks -name

Follow-up Comment #8, bug #20970 (project findutils): The fix is to use base_name (which malloc's) in combination with strip_trailing_slashes to get the correct string, then free the memory after the comparison. Both of those functions are provided by the dirname gnulib module. ___

[bug #20970] Trailing slash on directory arguments breaks -name

Follow-up Comment #7, bug #20970 (project findutils): The interp requires that -name not consider trailing slashes in the filename (but are considered in the pattern). The current gnulib last_component() and base_name() functions behave somewhat differently but in each case they leave one or m

[bug #20970] Trailing slash on directory arguments breaks -name

Follow-up Comment #6, bug #20970 (project findutils): The Austin Group interpretation was issued/approved today. http://www.opengroup.org/austin/interps/uploads/40/14959/AI-186.txt ___ Reply to this item at:

[bug #20970] Trailing slash on directory arguments breaks -name

Follow-up Comment #5, bug #20970 (project findutils): I've raised the issue with the Austin Group. Hopefully an interp will be reached before POSIX 200x is finalized: https://www.opengroup.org/sophocles/show_mail.tpl?CALLER=index.tpl&source=L&listname=austin-review-l&id=2512 _

[bug #20970] Trailing slash on directory arguments breaks -name

Follow-up Comment #4, bug #20970 (project findutils): Partly because we currently seem to be following common practice, I would be inclined to ask for a POSIX interp (i.e. for the current issues standard), or at least comment from the Austin Group, before changing our current behaviour. The is

[bug #20970] Trailing slash on directory arguments breaks -name

Follow-up Comment #3, bug #20970 (project findutils): More points of reference, seeing how coreutils handles extra trailing slashes (and adding the coreutils list for comments): $ mkdir -p dir/subdir $ touch q r $ mv -v q r dir `q' -> `dir/q' `r' -> `dir/r' $ # built names were compressed $

[bug #20970] Trailing slash on directory arguments breaks -name

Follow-up Comment #2, bug #20970 (project findutils): Just for fun, I tried it on FreeBSD as well, with identical results to GNU find. I had intuitively assumed that the -name thing was a no-brainer, for basically the reasons you mentioned (though I don't have a copy of POSIX available), but it

[bug #20970] Trailing slash on directory arguments breaks -name

Update of bug #20970 (project findutils): Status:None => Confirmed Assigned to:None => ericb ___ Reply to this item at:

[bug #20970] Trailing slash on directory arguments breaks -name

Update of bug #20970 (project findutils): Depends on: => bugs #20688 ___ Follow-up Comment #1: Part of me was inclined to mark this as invalid, since other implementations that claim to im

[bug #20970] Trailing slash on directory arguments breaks -name

URL: Summary: Trailing slash on directory arguments breaks -name Project: findutils Submitted by: rossaxe Submitted on: Tuesday 04/09/07 at 07:19 Category: find Severi