[meego-packaging] Guidance needed with package naming
shane.bryan at linux.intel.com
Fri Apr 1 09:38:06 PDT 2011
On Fri, 01 Apr 2011 19:28:16 +0300
Alberto Mardegan <mardy at users.sourceforge.net> 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?
I believe this is what "Provides" does, IIUC. So in your .yaml file it
would have the following under the signon-saslplugin section:
More information about the MeeGo-packaging