Roland Mainz wrote: > Brock Pytlik wrote: > >> http://cr.opensolaris.org/~bpytlik/ips-2672-v1/ >> has the patch. >> >> It makes case-insensitive search both possible and the default behavior. >> For local search, there's an option ( -I though I'm definitely open to >> alternatives -c?) that allows for case sensitive search. For protocol >> reasons, remote search is only case insensitive. There is a small (IMO) >> performance hit for both local and remote search. Case sensitive search >> still takes the same amount of time: .5-.6 seconds but case-insensitive >> search takes .7-.8 seconds. >> >> Remote search takes the biggest hit, going from .1-.2 seconds to .6-.7 >> seconds. >> > > Just curious: What does "remote search" mean in this case ? > Case-insenstive matching depends on the locale and AFAIK would require > to pass the the locale token (e.g. LANG, LC_*, LC_ALL) to the remote > site... > > ---- > > As Shawn said, remote search means searching the repositories of the authorities you have set. Since right now, we do no language specific adaptation, this would be an RFE. We use Python's .upper and .lower functions, which eventually call down to the C library functions tolower and toupper. Those use the locale for the program to determine the mapping between cases. If they don't recognize the character, they simply pass over it. Luckily, there is a solution, we can use Python's locale module to adapt out locale, but it's not thread safe, so making it work correctly in the current depot would not be trivial. Of course, we could roll our own lower and upper methods that didn't rely on a global locale and was thread safe, but that's also outside the scope of this bug. Please file a RFE for this.
Brock > Bye, > Roland > > _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
