Alexander Neundorf wrote:
>> > Now that it seems the shared-install-dirs feature can be removed, this
>> > could be good enough.
>> > It would imply that e-c-m will be updated relatively often
>>
>> Why would it need to be updated relatively often? Why does the removal of
>> the shared-install-dir
On Thursday 26 April 2012, Stephen Kelly wrote:
> Alexander Neundorf wrote:
> > I thought more about it.
> > How about that:
> >
> > find_package(KF5 COMPONENTS kcore kwidgets kitemmodels)
> >
> > searches in the normal cmake way for kcoreConfig.cmake, using
> > CMAKE_PREFIX_PATH and all that. Ad
Alexander Neundorf wrote:
> I thought more about it.
> How about that:
>
> find_package(KF5 COMPONENTS kcore kwidgets kitemmodels)
>
> searches in the normal cmake way for kcoreConfig.cmake, using
> CMAKE_PREFIX_PATH and all that. Additionally automatically also using
> KDEDIRS.
>
> Once it has
On Wednesday 25 April 2012, Stephen Kelly wrote:
> Alexander Neundorf wrote:
> >> I do not understand why we can not install multiple versions of a
> >> library to one prefix.
> >
> > E.g. because we don't have versioned include dirs, so there can be only
> > one version in one prefix (talking abo
Alexander Neundorf wrote:
> White: no kdelibs at all anymore, but 20 separate libraries. Gnome world ?
I'm not sure it will be so granular.
A lot of our code is for the benefit of 'KDE' only, and not useful for Qt
developers looking for re-usable libraries. The code that is useful already,
we
Alexander Neundorf wrote:
>> I do not understand why we can not install multiple versions of a library
>> to one prefix.
>
> E.g. because we don't have versioned include dirs, so there can be only
> one version in one prefix (talking about development installations).
Right, you were talking about
On Tuesday 24 April 2012 21:12:14 Alexander Neundorf wrote:
> On Tuesday 24 April 2012, David Faure wrote:
> ...
>
> > In fact, if a distro sets XDG_CONFIG_DIRS, then they'll have to not only
> > ensure KF5-based apps install into that config dir, but also every app
> > that
> > uses XDG (all Qt ap
On Saturday 21 April 2012, Sune Vuorela wrote:
> On 2012-04-20, Alexander Neundorf wrote:
> > * we will have a separate KF5 package, which will be a build-time
> > requirement for building KDE frameworks libraries. It will offer the
> > following features ** KDE approved compiler settings
> > ** K
On Tuesday 24 April 2012, David Faure wrote:
...
> In fact, if a distro sets XDG_CONFIG_DIRS, then they'll have to not only
> ensure KF5-based apps install into that config dir, but also every app that
> uses XDG (all Qt apps, probably all gnome apps, etc. etc.). This doesn't
> really seem doable,
On Tuesday 24 April 2012, Stephen Kelly wrote:
> Hi,
>
> I'm not certain we're understanding what the other is saying, and these
> emails are already too long and covering too many different subjects.
>
> I'll just select a few things to respond to.
Same here.
> > But, whenever I try to introdu
Hi,
I'm not certain we're understanding what the other is saying, and these
emails are already too long and covering too many different subjects.
I'll just select a few things to respond to.
> But, whenever I try to introduce versioned install dirs, nobody here wants
> to have them,
> so cur
On Saturday 21 April 2012 15:43:47 Alexander Neundorf wrote:
> If you say we don't need shared install locations (a KDE frameworks-using
> package picks up the custom install locations from the KDE frameworks it is
> built against if it is installed into the same prefix), then please first
> make
On 2012-04-20, Alexander Neundorf wrote:
> * we will have a separate KF5 package, which will be a build-time requirement
> for building KDE frameworks libraries. It will offer the following features
> ** KDE approved compiler settings
> ** KDE conforming install dirs
> ** finding consistent insta
On Saturday 21 April 2012, Alexander Neundorf wrote:
> On Saturday 21 April 2012, Stephen Kelly wrote:
...
> > What if I also have KCoreAddons installed in /opt/myotherkf5 ? How would
> > I decide which KF5-cmake-container-prefix to use? Environment variables
> > and wrapper scripts?
>
> As always
On Saturday 21 April 2012, Stephen Kelly wrote:
> Alexander Neundorf wrote:
> >> instead of maintaining a list of 'known' components. This would make the
> >> FindKDEFrameworks some kind of 'reflector' for finding frameworks which
> >> adds consistency of versions etc.
> >
> > I thought about this
Alexander Neundorf wrote:
>> instead of maintaining a list of 'known' components. This would make the
>> FindKDEFrameworks some kind of 'reflector' for finding frameworks which
>> adds consistency of versions etc.
>
> I thought about this.
> IMO it is a good thing to have a hardcoded list of known
Hi,
On Saturday 21 April 2012, Stephen Kelly wrote:
> Alexander Neundorf wrote:
> > Hi,
> >
> > so here's my proposal:
> >
> > * we will have a separate KF5 package, which will be a build-time
> > requirement for building KDE frameworks libraries. It will offer the
> > following features
> > **
Alexander Neundorf wrote:
> Hi,
>
> so here's my proposal:
>
> * we will have a separate KF5 package, which will be a build-time
> requirement for building KDE frameworks libraries. It will offer the
> following features
> ** KDE approved compiler settings
> ** KDE conforming install dirs
> **
Hi,
so here's my proposal:
* we will have a separate KF5 package, which will be a build-time requirement
for building KDE frameworks libraries. It will offer the following features
** KDE approved compiler settings
** KDE conforming install dirs
** finding consistent installations of the KDE fra
19 matches
Mail list logo
