On 4/1/2011 9:28 AM, Alberto Mardegan wrote:
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?
those shouldn't.... the ones using libs have the auto dependency...
and the ones using the daemon...
I'd like to fix them.
one option is to have the daemon do a Provides:
_______________________________________________
MeeGo-packaging mailing list
[email protected]
http://lists.meego.com/listinfo/meego-packaging
