|
It's kinda hard to describe, but my Fedora22 system at home has:
bzip2-libs-1.0.6-14.fc22.i686 bzip2-libs-1.0.6-14.fc22.x86_64 I didn't force the installation of these packages, but these co-exist just fine because (I presume) <name>.<arch> pair is different. I understand that pkgid (checksum) of the package is unique, but that's unique for pretty much anything, yet yum understands to "upgrade" certain packages instead of installing side-by-side. That was the gist of my question. If it isn't <name>.<arch>, I'd like to know what it is. Satoshi > To: yum@xxxxxxxxxxxxxxxxx > From: james-yum@xxxxxxx > Date: Mon, 27 Jul 2015 10:57:33 -0400 > Subject: Re: How does yum consider a package "unique"? > > Satoshi Yagi <marseille07@xxxxxxxxxxx> writes: > > > Hi, > > > > Looking at the explanation on filelists.xml.gz on this site http://www.slashroot.in/yum-repository-and-package-management-complete-tutorial, > > > > <package pkgid="deee52b24486906ee52576ee471b57061ccd5544" name="php-mbstring" arch="i386"> > > > > My gut feeling is that yum uses name.arch combination to uniquely identify a package. Could anyone confirm if this is correct? > > It depends what you mean by "unique", but it's never just n.a. > In the above xml fragment, pkgid would be the most unique thing as > that's the checksum of the package file (that's not completely unique > though because you can have the same package file in two different > repos.). > > -- > James Antill -- james@xxxxxxx > _______________________________________________ > Yum mailing list > Yum@xxxxxxxxxxxxxxxxx > http://lists.baseurl.org/mailman/listinfo/yum |
_______________________________________________ Yum mailing list Yum@xxxxxxxxxxxxxxxxx http://lists.baseurl.org/mailman/listinfo/yum
