Amit Laxmikant Pande wrote:
Have a basic question :
When updates (patches as well as packages) are hosted on a YUM
repository, how do we know to which platforms these updates are
applicable ?
For example, how can I know that the updates hosted are meant for
openSuse 10.3 or OpenSuse 11.0 or Fedora ?
Thanks,
Amit
We are trying to solve that problem for our next release. I just
commited the support some minutes ago.
The idea is, all of our products have a updatekey, which is unique. This
information is queryable on the system.
Repositories provide updates (patches) via the updateinfo.xml. In the
collection attribute which defines the packages for each distro for that
update we added an attribute id in addition to short and name. For all
the ids we have seen I save in the cache the list of keys.
Then a repo clams to provide updates for keys A and the second repo for
keys B,C and you have products A,C installed, you know you need both repos.
We use this method because a 3rd party repo can provide updates for 2
different products that share the same codebase (like SLES and SLED) so
there may be more than one target per repo.
Still, the keys the repo provides should be moved out of collection id,
because if there is no patches, then it would not work. It has to be
something in repomd.xml, which we can't touch much on the format side.
Duncan
_______________________________________________
Yum mailing list
Yum@xxxxxxxxxxxxxxxxxxxx
https://lists.dulug.duke.edu/mailman/listinfo/yum
