libmm-qt moved to frameworks/modemmanager-qt

[Daniel Vrátil]

On Saturday, April 04, 2015 12:18:45 PM Jan Grulich wrote:
> On Saturday 04 of April 2015 10:51 David Faure wrote:
> > On Tuesday 31 March 2015 23:37:22 Albert Astals Cid wrote:
> > > El Dimarts, 31 de març de 2015, a les 22:32:10, Jan Grulich va escriure:
> > > > On Tuesday 31 of March 2015 21:55 Albert Astals Cid wrote:
> > > > > El Dimarts, 31 de març de 2015, a les 13:15:30, Jan Grulich va
> 
> escriure:
> > > > > > Hi,
> > > > > > 
> > > > > > we have finally moved libmm-qt library to frameworks and renamed
> > > > > > it
> > > > > > to
> > > > > > modemmanager-qt. It's now going to be released together with KDE
> > > > > > Frameworks
> > > > > > 5 and not with Plasma 5 as it was until now. The upcoming release
> > > > > > is
> > > > > > not
> > > > > > ABI/API compatible with the previous releases, so if you are going
> > > > > > to
> > > > > > keep
> > > > > > Plasma 5.2.x you need to keep also libmm-qt in the version
> > > > > > released
> > > > > > together with it.
> > > > > 
> > > > > Are the two things at least co-installable?
> > > > 
> > > > Unfortunately no, but we can maybe provide an updated tarball with
> > > > plasma-
> > > > nm-5.2.2 which works with the new version of mm-qt.
> > > 
> > > Either that or you make sure David puts a big fat warning when releasing
> > > the new frameworks version.
> > > 
> > > Ideally what you should do is don't break backwards compatibility, and
> > > if
> > > you're going to break it, just call it V2, if i was a packager i'd be
> > > pretty unhappy you've put such a burden on me now, having to forget when
> > > to exchange some packages depending on some other package that also
> > > depends on some other package probably.
> > 
> > So what is happening in the end? I'm making the release today if all goes
> > well, and the above looks ... messy.
> 
> I would like to have it released now. I know it's a bit messy, but it was
> our last chance to rework the library and change it properly. The only
> thing what needs to be changed in plasma-nm are 2 signal signatures, so we
> can just release an updated version.

Or you could release the framework just before Plasma 5.3 and have plasma-nm 
depend on that version? It would certainly make it easier for packagers to 
handle the situation :)

> 
> Regards,
> Jan

-- 
Daniel Vrátil
www.dvratil.cz | dvratil at kde.org
IRC: dvratil on Freenode (#kde, #kontact, #akonadi, #fedora-kde)

GPG Key: 0x4D69557AECB13683
Fingerprint: 0ABD FA55 A4E6 BEA9 9A83 EA97 4D69 557A ECB1 3683
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20150404/1db10a27/attachment.sig>