Re: Wildcard bug or feature?

On Fri, 23 Mar 2007 12:53:05 -0400, Steve Brown wrote:

> Due to disk space constraints on my notebook, I was unable to update 435 
> applications all at once.  Wanting to do my updates in smaller batches, 
> I tried 'yum update apr-*' and was happy to find that I could use 
> wildcards to specify smaller groups of applications to update.  Next, I 
> tried 'yum update a* b* c* d*' figuring I would do four letters of the 
> alphabet at a time.  The prompt said I would only be updating 2 
> applications, though I know from my 'yum list updates' list that there 
> are many more applications to be updated beginning with those letters.
> 
> Next, I tried 'yum update a*' and noticed that there were may lines 
> saying there was no match followed by the name of a file that started 
> with 'a' that was in the current directory.  When I moved into an empty 
> subdirectory and ran 'yum update a*', it ran exactly as I had hoped.
> 
> If this is a bug, please fix it.  If it's a feature, please explain.
> 
> By the way, something like 'yum -n ## update' where ## is the number of 
> applications to update would be helpful in this situation, or better 
> yet, have yum clean up after itself every ## updates.

Don't let bash expand the star names.  :-)  It only passes the unexpanded
star name when it fails.

Do 'yum update "a*"' or 'yum update a\*'.  

	-Paul