ECM version changed (Re: KDE Frameworks 5 TP1 tarballs)
Albert Astals Cid
aacid at kde.org
Tue Jan 7 18:33:45 UTC 2014
El Dimarts, 7 de gener de 2014, a les 09:40:39, David Faure va escriure:
> On Sunday 05 January 2014 20:43:14 šumski wrote:
> > On Sunday 05 of January 2014 12:40:05 David Faure wrote:
> > ...
> >
> > > You can find it in kde-build-metadata/dependency-data-kf5-qt5, attached
> > > here for convenience.
> >
> > Great, just a few questions ;-)
> > 1) Is it expected that extra-cmake-modules and attica have the versioning
> > scheme as other frameworks? i.e. are they considered as part of KF5 in
> > future?
>
> Attica yes.
> ECM no.
> You're right, the ECM version number is probably wrong, since ECM internally
> says version 0.0.9.
>
> The packaging scripts don't really support different version numbers for
> different modules... well I reran them for ECM alone.
Shouldn't ecm be basically *not* be packaged with frameworks? I.e. do you plan
to keep releasing ecm every time you release frameworks? I understood it was a
separate project and thus the separate versioning.
Cheers,
Albert
>
> @PACKAGERS: extra-cmake-modules-0.0.9 is up, replacing the 4.95.0 version.
> git-sha1 and sha256sum:
>
> 83dbc09088b53196993b13318e84459eeb26e8e4
> b8e0f0a9db14583aead8d60ff03ee2734a26a2f9881e69719efc81ec2e74da85
> sources/extra-cmake-modules-0.0.9.tar.xz
>
> > 2) Wrt. co-installability: atm KF5 cannot be installed side by kdelibs4 in
> > same prefix due to file conflicts (e.g. kconfig_compiler, kmailservice,
> > ktelnetservice, some DBus interface files) - is this also longer term
> > plan,
> > or it just hasn't yet been 100% tackled?
>
> I'll let Jonathan Riddell reply to that since he was spearheading the
> effort. I don't mind renaming these binaries, if that helps (but after
> TP1).
More information about the release-team
mailing list