Re: Review Request 119849: Improve CMAKE error message when XRender or XFixes are missing

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/119849/#review64890 --- Ship it! best would of course be to migrate away from those X

Re: How to promote less mature Frameworks?

On Tuesday 19 August 2014 22:39:32 Cornelius Schumacher wrote: > On Tuesday 19 August 2014 09:33:07 Kevin Ottens wrote: > > On Tuesday 19 August 2014 08:44:10 David Faure wrote: > > > IMHO the solution is just to publicize the upcoming frameworks > > > somewhere. > > > > Which shouldn't be that ha

Unsolicited email delivered to the mailing list

Hi all, Just to let you know, the delivery of unsolicited email to these mailing lists recently is in the process of being dealt with. This was not the result of a fault in Mailman - the identity of a mailing list member has been impersonated to abuse our lists. The ultimate originating sender (N

I think you should join 101 Pines/Horseshoe Lake's private website

Hello, Valorie Zimmerman invites you to join your 101 Pines/Horseshoe Lake neighbors on Nextdoor. Nextdoor is a free and private social network that your neighbors are using. Valorie wrote: "Our neighborhood is using a private online network called Nextdoor 101 Pines/Horseshoe Lake. On our Nex

Re: Review Request 119849: Improve CMAKE error message when XRender or XFixes are missing

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/119849/ --- (Updated Aug. 20, 2014, 12:55 vorm.) Review request for KDE Frameworks.

Re: Proposal to improving KDE Software Repository Organization

On Wed, Aug 20, 2014 at 9:39 AM, Michael Pyne wrote: > On Tue, August 19, 2014 10:18:17 David Faure wrote: >> On Tuesday 19 August 2014 19:10:14 Ben Cooksley wrote: >> > The old kf5-qt5 / latest-qt4 names are being mapped to division / >> > track combinations. They are otherwise not used. >> >> Ah

Re: Proposal to improving KDE Software Repository Organization

On Tue, August 19, 2014 10:18:17 David Faure wrote: > On Tuesday 19 August 2014 19:10:14 Ben Cooksley wrote: > > The old kf5-qt5 / latest-qt4 names are being mapped to division / > > track combinations. They are otherwise not used. > > Ah! > > > Just a clarification though: there would only be tw

Review Request 119849: Improve CMAKE error message when XRender or XFixes are missing

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/119849/ --- Review request for KDE Frameworks. Repository: kwindowsystem Descriptio

Re: Replacement for kde4_add_app_icon ?

On 12 Aug 2014, at 12:52 , Albert Astals Cid wrote: > Hi, i've been porting some of my apps to KF5 work and I'm noticing there > doesn't seem to be (or i can't find) a replacement for kde4_add_app_icon. > > This seems like a problem for the support in windows/macosX. Is there any > plan > to

Re: How to promote less mature Frameworks?

El Dimarts, 19 d'agost de 2014, a les 08:44:10, David Faure va escriure: > On Friday 15 August 2014 12:51:58 Kevin Ottens wrote: > > On Friday 15 August 2014 09:34:04 Alex Merry wrote: > > > On Friday 15 August 2014 10:21:57 Mark Gaiser wrote: > > > > On Fri, Aug 15, 2014 at 12:12 AM, Àlex Fiestas

OSX/CI: kactivities can't be build due to failing to locate framework kdeclarative

When trying to build kactivities an error occurs on OSX due to inability to locate kdeclarative: --- CMake Warning (dev) at /opt/kde/install/darwin/mavericks/clang/kf5-qt5/kdesupport/extra-cmake-modules/inst/share/ECM/find-modules/FindKF5.cmake:52 (message): Your project should require at le

Re: kcoreaddons fails to build properly on OSX/CI (was OSX/CI: kauth fails to build )

Hi Aleix & Ben, On 13 Aug 2014, at 10:51 , Aleix Pol wrote: > I'm unsure, try cleaning the build directory and trying again? > There certainly hasn't been a change on the kf5 side, that I know of at least. following you guys’ advice, I could verify that there was nothing new, neither in ECM nor

Re: How to promote less mature Frameworks?

On Tuesday 19 August 2014 09:33:07 Kevin Ottens wrote: > On Tuesday 19 August 2014 08:44:10 David Faure wrote: > > > IMHO the solution is just to publicize the upcoming frameworks somewhere. > > Which shouldn't be that hard, it's "only" about processing the yaml file and > creating a page listing

Re: Review Request 119809: KIO: New job RestoreJob, public API KIO::restoreFromTrash().

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/119809/ --- (Updated Aug. 19, 2014, 8:36 p.m.) Status -- This change has been ma

Re: Review Request 119846: qtcontrols port for checkbox and radiobutton

> On Aug. 19, 2014, 7:43 p.m., David Edmundson wrote: > > src/declarativeimports/plasmacomponents/qml/styles/CheckBoxStyle.qml, line > > 51 > > > > > > checked isn't a boolean, it's an enum of the checked, partia

Re: Kioslave repos

On Tuesday 01 July 2014 22:25:15 Jonathan Riddell wrote: > On Tue, Jul 01, 2014 at 11:25:11PM +0200, David Faure wrote: > > On Sunday 27 April 2014 19:35:37 I wrote: > > > > * place that repo in kde/ or kde/ in the projects.kde.org > > > > hierarchy, so that it gets released with the KDE Applicatio

Re: What to do with autostart scripts? (kinit / ksmserver problem)

On Wednesday 09 July 2014 14:24:37 Luca Beltrame wrote: > Hello, > > commit f913e251fe66e22606c380a8cc0ddc8c69e3c07d in plasma-workspace removed > autostart support in ksmserver because it caused .desktop files to be > autostarted twice (one for kinit, and one for ksmserver). > > I just noticed t

Re: Review Request 119846: qtcontrols port for checkbox and radiobutton

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/119846/#review64882 --- src/declarativeimports/plasmacomponents/qml/styles/CheckBoxSt

Re: Review Request 119808: Move module metadata to after class picker

> On Aug. 19, 2014, 10:19 a.m., Aleix Pol Gonzalez wrote: > > I think it's disputable that the developers will want to interact with the > > "File List" more often. I think this shows we want a new design after all. > > > > For the moment, I won't +1 or -1. I'm admittedly going off how I perso

Re: Review Request 119798: Generating PkgConfig files from ECM

> On Aug. 15, 2014, 8:20 a.m., Alex Merry wrote: > > modules/ECMGeneratePkgConfigFile.cmake, line 47 > > > > > > This belongs in KDEInstallDirs.cmake, not here (as > > CMAKE_INSTALL_PKGCONFIGDIR, ideally). Projec

Review Request 119846: qtcontrols port for checkbox and radiobutton

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/119846/ --- Review request for KDE Frameworks and Plasma. Repository: plasma-framewor

Re: How to promote less mature Frameworks?

On Tuesday 19 August 2014 16:53:58 Sebastian Kügler wrote: > On Tuesday, August 19, 2014 09:33:07 Kevin Ottens wrote: > > > Wouldn't early adopters just checkout and build from git ? > > > > Well, I guess some of them might just want to grab something and run with > > it. Maybe not the majority i

Re: How to promote less mature Frameworks?

On Tuesday, August 19, 2014 09:33:07 Kevin Ottens wrote: > > Wouldn't early adopters just checkout and build from git ? > > Well, I guess some of them might just want to grab something and run with > it. Maybe not the majority indeed... I think in this case we want to encourage picking it from G

Re: How to promote less mature Frameworks?

On Tuesday 19 August 2014 15:09:46 Aleix Pol wrote: > On Tue, Aug 19, 2014 at 2:04 PM, Kevin Ottens wrote: > > I'd wait for the demand for that. api.kde.org is already very loaded in > > information no need to add even more IMO. > > Well, we did some information unloading work back in Randa. Mayb

Re: How to promote less mature Frameworks?

On Tue, Aug 19, 2014 at 2:04 PM, Kevin Ottens wrote: > On Tuesday 19 August 2014 12:22:17 Aleix Pol wrote: > > On Tue, Aug 19, 2014 at 9:33 AM, Kevin Ottens wrote: > > > On Tuesday 19 August 2014 08:44:10 David Faure wrote: > > > > IMHO the solution is just to publicize the upcoming frameworks >

Re: How to promote less mature Frameworks?

On Tuesday 19 August 2014 12:22:17 Aleix Pol wrote: > On Tue, Aug 19, 2014 at 9:33 AM, Kevin Ottens wrote: > > On Tuesday 19 August 2014 08:44:10 David Faure wrote: > > > IMHO the solution is just to publicize the upcoming frameworks > > > somewhere. > > > > Which shouldn't be that hard, it's "on

Re: Review Request 119798: Generating PkgConig files from ECM

> On Aug. 15, 2014, 8:20 a.m., Alex Merry wrote: > > modules/ECMGeneratePkgConfigFile.cmake, line 47 > > > > > > This belongs in KDEInstallDirs.cmake, not here (as > > CMAKE_INSTALL_PKGCONFIGDIR, ideally). Projec

Re: Review Request 119798: Generating PkgConfig files from ECM

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/119798/ --- (Updated Aug. 19, 2014, 11:34 a.m.) Review request for Build System, KDE

Re: Proposal to improving KDE Software Repository Organization

On Tue, Aug 19, 2014 at 3:54 AM, Michael Pyne wrote: > Hi all, > > Ben Cooksley and I would like to get some feedback on further evolutions to > the organization structure we employ for the repositories at git.kde.org, > to > allow our current usage of CI even as we move farther into the KF5-base

Re: How to promote less mature Frameworks?

On Tue, Aug 19, 2014 at 9:33 AM, Kevin Ottens wrote: > On Tuesday 19 August 2014 08:44:10 David Faure wrote: > > On Friday 15 August 2014 12:51:58 Kevin Ottens wrote: > > > And that's the problem if we release them. If it's released "with the > > > rest" expect people to have wrong expectations a

Re: Review Request 119808: Move module metadata to after class picker

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/119808/#review64831 --- I think it's disputable that the developers will want to inter

Re: Proposal to improving KDE Software Repository Organization

On Tuesday 19 August 2014 19:10:14 Ben Cooksley wrote: > The old kf5-qt5 / latest-qt4 names are being mapped to division / > track combinations. They are otherwise not used. Ah! > Just a clarification though: there would only be two divisions for the > above scenario: Plasma5 and KF5. > Plasma5 w

Re: Review Request 119773: Launch scripts in autostart-directories

--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/119773/ --- (Updated Aug. 19, 2014, 7:45 a.m.) Status -- This change has been di

Re: Review Request 119773: Launch scripts in autostart-directories

> On Aug. 19, 2014, 6:41 a.m., David Faure wrote: > > In the KF5 world even more so than before, all the autostart code should be > > in workspace rather than in kinit. This is really a workspace feature, > > starting a single app based on KF5 doesn't and shouldn't start anything. > > > > kioc

Re: How to promote less mature Frameworks?

On Tuesday 19 August 2014 08:44:10 David Faure wrote: > On Friday 15 August 2014 12:51:58 Kevin Ottens wrote: > > And that's the problem if we release them. If it's released "with the > > rest" expect people to have wrong expectations about them. > > > > A possibility would be perhaps to produce n

Re: Proposal to improving KDE Software Repository Organization

On Tue, Aug 19, 2014 at 6:55 PM, David Faure wrote: > Nice work. Thanks. > > Just one thing: > > On Monday 18 August 2014 21:54:40 Michael Pyne wrote: >> So "kf5-qt5" might mean "KF5/Devel, Plasma5/Devel, etc." while >> "kf5-qt5-stable" might mean "KF5/Devel, Plasma5/Stable, etc.". > > This