On 01/07/2014 07:40 PM, David Faure wrote:
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.
Which tier is attica part of? It seems to
On Monday 20 January 2014 01:44:37 šumski wrote:
On Saturday 11 of January 2014 11:15:47 Michael Palimaka wrote:
...
Any news on renaming the remaining binaries?
Just to follow up on this - Jonathan has meanwhile been quite busy =)
Attica is now adjusted so it can co-exist with Qt4
On Monday, January 20, 2014 01:44:37 AM šumski wrote:
On Saturday 11 of January 2014 11:15:47 Michael Palimaka wrote:
...
Any news on renaming the remaining binaries?
Just to follow up on this - Jonathan has meanwhile been quite busy =)
Attica is now adjusted so it can co-exist with Qt4
El Dilluns, 20 de gener de 2014, a les 23:39:32, Valentin Rusu va escriure:
On Monday, January 20, 2014 01:44:37 AM šumski wrote:
On Saturday 11 of January 2014 11:15:47 Michael Palimaka wrote:
...
Any news on renaming the remaining binaries?
Just to follow up on this - Jonathan
On Monday, January 20, 2014 11:48:51 PM Albert Astals Cid wrote:
El Dilluns, 20 de gener de 2014, a les 23:39:32, Valentin Rusu va escriure:
On Monday, January 20, 2014 01:44:37 AM šumski wrote:
On Saturday 11 of January 2014 11:15:47 Michael Palimaka wrote:
...
Any news on
On Saturday 11 of January 2014 11:15:47 Michael Palimaka wrote:
...
Any news on renaming the remaining binaries?
Just to follow up on this - Jonathan has meanwhile been quite busy =)
Attica is now adjusted so it can co-exist with Qt4 version, and we have 3
binaries left, which all have opened
On 01/07/2014 07:40 PM, David Faure wrote:
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
On Wednesday 08 January 2014 13:29:34 Daniel Vrátil wrote:
On Monday 06 of January 2014 23:13:22 Jonathan Riddell wrote:
On Sun, Jan 05, 2014 at 08:43:14PM +0100, šumski wrote:
On Sunday 05 of January 2014 12:40:05 David Faure wrote:
...
You can find it in
Le mardi 7 janvier 2014 00:04:00 Kevin Kofler a écrit :
On Monday 06 January 2014 at 16:54:13, Allen Winter wrote:
rename then to kconfig_compiler5, kmailservice5, ktelnetservice5 ... ?
+1 to that!
Otherwise we have to do that at distro level in Fedora (see e.g. the patch
we're applying
On Monday 06 of January 2014 23:13:22 Jonathan Riddell wrote:
On Sun, Jan 05, 2014 at 08:43:14PM +0100, š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,
On Tue, Jan 07, 2014 at 09:40:39AM +0100, David Faure wrote:
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.
shall I make attica a kde
On Wednesday 08 January 2014 14:15:23 Jonathan Riddell wrote:
On Tue, Jan 07, 2014 at 09:40:39AM +0100, David Faure wrote:
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
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
On Tuesday 07 January 2014 at 00:27:37, šumski wrote:
(Yes, i'm aware of the https://community.kde.org/Frameworks/Coinstallability
page - but libraries are either co-installable, or not, i.e. 'they are co-
installable if you put certain files in package A, others in package B,
then you
On Tue, Jan 07, 2014 at 06:07:16PM +0100, Kevin Kofler wrote:
On Tuesday 07 January 2014 at 00:27:37, šumski wrote:
(Yes, i'm aware of the https://community.kde.org/Frameworks/Coinstallability
page - but libraries are either co-installable, or not, i.e. 'they are co-
installable if you put
On Tue, Jan 07, 2014 at 06:13:12PM +0100, Kevin Kofler wrote:
On Tuesday 07 January 2014 at 00:27:37, šumski wrote:
This would leave KAuth's DBus configuration file + Solid's, KGlobalAccel's,
KJobWidgets, KNotifications and KWallet DBus interface files left to adjust.
And also library
On Tuesday 07 January 2014 at 00:27:37, šumski wrote:
This would leave KAuth's DBus configuration file + Solid's, KGlobalAccel's,
KJobWidgets, KNotifications and KWallet DBus interface files left to adjust.
And also library symlinks, or do all the libraries have different unversioned
names now?
On Tuesday 07 of January 2014 18:13:12 Kevin Kofler wrote:
And also library symlinks, or do all the libraries have different
unversioned names now?
Libraries themselves are completely renamed: only attica's symlink and pc file
are of the same name as Qt4 version (the so is bumped to 1.0.0
On Tue, Jan 07, 2014 at 06:33:45PM +0100, šumski wrote:
On Tuesday 07 of January 2014 18:13:12 Kevin Kofler wrote:
And also library symlinks, or do all the libraries have different
unversioned names now?
Libraries themselves are completely renamed: only attica's symlink and pc
file
On Tuesday 07 of January 2014 17:38:55 Jonathan Riddell wrote:
Voila (for attica) https://git.reviewboard.kde.org/r/114899/
Great! =)
Will try it ASAP,
(needs also according changes in KNewStuff, and other indirect deps, yes?)
Cheers,
Hrvoje
Jonathan
On Tuesday 07 January 2014 at 18:33:45, šumski wrote:
polkit- qt-1, where the libs have both the same name and version on both
Qt4 and 5 case (though polkit-qt-1 is optional).
Ouch, that really needs fixing!
How many client modules will be affected by a rename? In Qt/KDE 4 land, from
the
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.
On Tuesday 07 January 2014 19:33:45 Albert Astals Cid wrote:
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.
That's the goal, but ATM
On Tuesday 07 January 2014 19:33:45 Albert Astals Cid wrote:
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.
Separate versioning
On Tuesday 07 of January 2014 19:08:39 Kevin Kofler wrote:
Ouch, that really needs fixing!
How many client modules will be affected by a rename? In Qt/KDE 4 land, from
the stuff packaged in Fedora 18, I see kdelibs (KAuth), polkit-kde and
razorqt- policykit-agent, but obviously we'd rename
On Sunday, January 05, 2014 08:43:14 PM š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
On Monday 06 January 2014 at 16:54:13, Allen Winter wrote:
rename then to kconfig_compiler5, kmailservice5, ktelnetservice5 ... ?
+1 to that!
Otherwise we have to do that at distro level in Fedora (see e.g. the patch
we're applying to kdelibs 4) and we don't like having to do that.
On Monday 06 of January 2014 16:54:13 Allen Winter wrote:
rename then to kconfig_compiler5, kmailservice5, ktelnetservice5 ... ?
Sounds good to me - as Kevin noted, would be much better to do that upstream,
then to see all distros carry the same patches before the first release is even
made
Le mardi 7 janvier 2014 00:04:00 Kevin Kofler a écrit :
On Monday 06 January 2014 at 16:54:13, Allen Winter wrote:
rename then to kconfig_compiler5, kmailservice5, ktelnetservice5 ... ?
+1 to that!
Otherwise we have to do that at distro level in Fedora (see e.g. the patch
we're applying
The first technical preview of KF5 is up for packaging, on depot.kde.org in
unstable/frameworks/4.95.0
I haven't done a release in a very VERY long time, so tell me if I forgot to
do anything...
Since this is the first KF5 release, one thing that you guys might need for
packaging is the
On Sunday 05 January 2014 12:40:05 David Faure wrote:
And now the bad news: we'd like to release on January 7.
But this is just a technical preview of something technical (= not usable by
end users), I'm not sure if we *need* to have binary packages by that date.
Indeed it's not critical IMO.
Stupid bugged GMail app...resending to ML.
On Jan 5, 2014 12:40 PM, David Faure fa...@kde.org wrote:
The first technical preview of KF5 is up for packaging, on depot.kde.orgin
unstable/frameworks/4.95.0
I haven't done a release in a very VERY long time, so tell me if I forgot
to
do
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.
33 matches
Mail list logo
