On 04/01/2011 06:39 PM, Arjan van de Ven wrote: > On 4/1/2011 5:06 AM, Alberto Mardegan >> And turn libsignon as a metapackage depending on libsignon-qt (which >> in turn will depend on signond), and libsignon-saslplugin a >> metapackage depending on signon-saslplugin. Same for all other plugins. > > please don't do a meta package.
OK. But if I don't provide packages with the same names as the existing ones, won't this break the images? I understand that building will not be affected, since what matters there is the pkg-config file name (which won't change), but what about some client RPMs which might have explicit dependency to "libsignon", for instance? >> And if it does, any clues on how to implement this? In particular, I >> don't know how to write the package names in the spec file (given that >> not all of them have the same prefix). > > the magic is the "-n" option... Thanks, I will use it! Ciao, Alberto -- http://blog.mardy.it <- geek in un lingua international! _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
