2012/5/6 Stephen Kelly :
> Kevin Ottens wrote:
>
>> * kidletime, the only one not started, somewhat independent though, Dario
>> is the maintainer.
>
> I notice that this one uses a lot of X11.
>
> Is porting from xlib to xcb part of considering something like this 'done'?
> KWindowSystem still use
On Sunday 06 May 2012 18:41:31 Stephen Kelly wrote:
> Kevin Ottens wrote:
> > * kidletime, the only one not started, somewhat independent though, Dario
> > is the maintainer.
>
> I notice that this one uses a lot of X11.
>
> Is porting from xlib to xcb part of considering something like this 'done'
On Sunday 06 May 2012 18:38:13 Stephen Kelly wrote:
> Kevin Ottens wrote:
> > # What happened in April?
> > Unfortunately no split was completed in April. It mainly comes from less
> > availability of the volunteers for those splits than expected.
>
> For those who don't know (kcd, presumably), apa
Kevin Ottens wrote:
> * kidletime, the only one not started, somewhat independent though, Dario
> is the maintainer.
I notice that this one uses a lot of X11.
Is porting from xlib to xcb part of considering something like this 'done'?
KWindowSystem still uses xlib, and was moved out of staging
Kevin Ottens wrote:
> Hello,
>
> May is upon us, flowers are blooming, temperature is rising... time for
> another quick recap on the progresses (or lack thereof) in the kdelibs
> splitting department. I'll also present the revised backlog for May and
> following months.
>
>
>
> # What happene
Stephen Kelly wrote:
> If it is, then I'd resubmit my proposal to have:
>
> include(ItemModelsConfigCommon.cmake)
>
> inside ItemModelsConfig.cmake, and generate it in the CMakeLists.txt
And by the way I also think we've covered all the discussion points needed
in this thread and it's time to
Alexander Neundorf wrote:
> URL and DESCRIPTION belong to the used project, so they are candidates for
> being set in the Config.cmake file.
> But there are two downsides of setting them in the Config file:
> - the information where to get the package is not present when the package
> is not presen
Hello,
May is upon us, flowers are blooming, temperature is rising... time for
another quick recap on the progresses (or lack thereof) in the kdelibs
splitting department. I'll also present the revised backlog for May and
following months.
# What happened in April?
Unfortunately no split was co
On Sunday 06 May 2012, Stephen Kelly wrote:
> Alexander Neundorf wrote:
> >> kf5_do_common_stuff() # TODO: Get better name
> >
> > Where should this macro come from ?
> > Should this be expanded from @PACKAGE_INIT@ or from an included file ?
> > From an included file would be bad, this would add c
Alexander Neundorf wrote:
>> kf5_do_common_stuff() # TODO: Get better name
>
> Where should this macro come from ?
> Should this be expanded from @PACKAGE_INIT@ or from an included file ?
> From an included file would be bad, this would add compatibility issues
> for the included file.
You mean i
On Sunday 06 May 2012, Stephen Kelly wrote:
> Alexander Neundorf wrote:
> >> >> Why do we need a use file? Qt 5 doesn't create or install them.
> >> >
> >> > You added it, so I thought you want to have it.
> >> > If not, let's remove it.
> >>
> >> Yes.
> >
> > Ok. I'll remove them in the next da
On Sunday 06 May 2012, Stephen Kelly wrote:
> Alexander Neundorf wrote:
> > attached are prototypes.
> >
> > Please have a look (ignore the version-related stuff for now).
> >
> > The Use-file is not there anymore, and the Config.cmake.in file is not
> > there anymore.
> > Instead it is now gener
12 matches
Mail list logo
