-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Tim wrote:
> On Wed, 2006-06-07 at 21:35 +0200, Jeremy Thompson wrote:
>> # yum --exclude evolution\* update
>
> There should be an equals sign between exclude and the package name
> (see the yum man file).
>
> e.g. yum --exclude=evolution\* update
The equals is optional and the command will work with or without it.
(Or fail the same way with or without it, in Jeremy's case. :)
This is something that depends a lot on what's parsing the command
line input. For yum it uses python's optparse module and option
arguments can be specified with or without the =. At least, that's
how it works as far as I understand and I've tested it both ways. If
that doesn't work in some cases, I'd be surprised. But it wouldn't be
the first time I was surprised (nor wrong either).
> I don't know about the need for escaping the wildcard, though. I've
> not tried that sort of thing. I wouldn't have thought it necessary,
> as you're not listing local files, you're providing a package name
> to the program.
I thought that bash would still try to expand it. Actually testing
with yum list evolution* does indeed produce a list of all the
packages beginning with evolution. So I learned something new today.
I'll still probably quote or backmask * when I do this sort of thing,
just to avoid being surprised when I do happen to have local files
matching the string.
- --
Todd OpenPGP -> KeyID: 0xD654075A | URL: www.pobox.com/~tmz/pgp
======================================================================
water, taken in moderation, cannot hurt anybody.
-- mark twain
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: When crypto is outlawed bayl bhgynjf jvyy unir cevinpl.
iG0EARECAC0FAkSHO08mGGh0dHA6Ly93d3cucG9ib3guY29tL350bXovcGdwL3Rt
ei5hc2MACgkQuv+09NZUB1rKNwCgkxZOWrn/jbUo7B9iDqb59tZiWoQAoILi6zqg
CbjWUjCbON/R6u/IKFyB
=7iek
-----END PGP SIGNATURE-----
