On Thursday 23 of October 2014 16:33:48 Jeremy Whiting wrote: > ---------- Forwarded message ---------- > From: Jeremy Whiting <[email protected]> > Date: Thu, Oct 23, 2014 at 8:31 AM > Subject: kdeedu-data > To: kde-packager <[email protected]>, KDE Edu <[email protected]> > > > Hey packagers, > > A quick heads up about kdeedu-data strangeness. > > The upcoming KDE Applications 14.12 release will have some > applications based on kdelibs4 and others based on kf5. Because some > applications that use libkdeedu/libkeduvocdocument are going to be > still based on kdelibs4 while others have already been ported to qt5 > and kf5 there will be both libkdeedu and libkeduvocdocument tarballs > released. Because both used to contain a handful of kvtml files, we > moved them out into kdeedu-data which both libkdeedu and > libkeduvocdocument should depend on (or at least khangman(kdelibs4) > and kanagram(libkeduvocdocument) should depend on in order to run. > > Now kdeedu-data uses ecm instructions to build like other kf5 based > applications. Is that going to be a problem to make both khangman and > kanagram run time depend on these packages, while kdeedu-data at build > time requires ecm to build? > > I'm open to other solutions, but this is the best we could come up > with at this time. But will remaining kde4 apps know to find ${DATA_INSTALL_DIR} spoken with e-c-m language? IOW, by default, kde4's ${DATA_INSTALL_DIR} = "share/apps", with e- c-m it's "share"...
Cheers, Hrvoje > thanks, > Jeremy > _______________________________________________ > release-team mailing list > [email protected] > https://mail.kde.org/mailman/listinfo/release-team
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ release-team mailing list [email protected] https://mail.kde.org/mailman/listinfo/release-team
