Re: specifying case-ignore in updatedb & find.

[James Youngman]

On Wed, Nov 10, 2010 at 9:17 AM, Linda A. Walsh <address@hidden> wrote:
>
>
>
> There doesn't seem to be a way to specify paths in 'updatedb' to allow for
> case-insentive matching.

Yes; updatedb was originally designed for Unix-like systems and when
we started supporting non-Unix filesystems, nobody really audited
everything to make a complete list of what would need to be changed.

> Also, the in order for the problem to be solved completely, find has to be
> fixed as well.

Certainly I can't see a way to make the change you have in mind in an
efficient way without it (since e.g. grep -v would be very expensive).


> The part that would be, I think, updatedb-specific is the --prunepaths
> option.  There needs to be an --iprunepaths option.  The former uses
> -regex to do exception matching, while the later would use -iregex to do
> matching.
>
>
> The part that's common to both, is that while find has -iXXXXX options to
> parallel -XXXXX options that ignore case, it needs a way to tell it to
> ignore case on the starting pathnames just like it has options to tell
> it to process them as symlinks or not.
>
> Comments?
>
> Should I just submit it to the bug database?  If so, should there be
> separate issues for find and updatedb?

Let's start with find.

> Separate ones for updatedb involving
> --prunepaths vs. the starting paths (since they involve separate
> dependencies in find?)
>
>
> Thanks,
> Linda
>
>
> (sorry for any confusion in mentioning the find and updatedb problems in
> terms of specific applications.  I can see how mentioning 3rd party apps
> might distract from the essential problem areas).
>
>
>
>
>
>
>
>