atrpms kernel modules

[Paul Howarth]

Michael H. Warfield wrote:
> On Tue, 2006-07-18 at 14:41 +0100, Paul Howarth wrote:
>> Neither yum nor rpm know which packages you want to get from which repo 
>> unless you explictly tell them. The big list of packages you get are 
>> packages (or their dependencies) that you already have on your system 
>> (from some repo other than ATrpms) that have "later" versions in ATrpms. 
>> Since you told yum that you wanted to update all of the packages on your 
>> system to the latest versions, and to get packages from ATrpms, it tried 
>> to do what it was told and you got the big list.
> 
> 	Yes, and agreed and understood.  But also one that lead smack into a
> critical dependency failure that killed the update cold.  A dependency
> failure that only occurs when ATrpms is included.

To be fair, this could happen when any two repos are used that have 
packages with the same names (or having the same "Provides" as far as 
RPM is concerned). It's not specific to ATrpms.

>> If you don't want that to happen, you could use an "includepkgs" entry 
>> in your ATrpms repo file to list only those packages you want to pull 
>> from ATrpms.
> 
> 	Does that allow for "wildcarding".  IOW, can I do an includepkgs for
> zaptel-kmdl-*_FC5xen0-*.fc5.at ?  If not, that's not going to work for
> the kmdl packages because that versioning is included in the package
> names (which doesn't work for updates anyways, which we've already
> established).

I know the "excludepkgs" option supports some glob-style wildcards so 
I'd guess that "includepkgs" did too. Not sure how good the wildcard 
support is though, e.g. if it handles "*" in the middle of a name. Try 
it and see :-)

Paul.