You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to add it to the Chum Qt5/KF5 list of applications, HOWEVER there are a couple of things which might preclude that:
It has a couple of dependencies which are not yet in chum
Some of the above are not KF5 but KPIM5 packages. AFAICS there are not yet any of those in Chum. Are they fine, and do we maybe need another package clas for them (opt-kpim-foo)?
It depends on kf5-kcalendarcore and kf5-kcontacts; these compile fine, can be used as build deps, but of course are not useful on SFOS. Is that ok?
It depends on kitinerary (not to be confused with Itinerary!) which needs private headers from poppler to build. Poppler is a Jolla-supplied package and therefore can not be in Chum. The Jolla package does not package the private headers.
The text was updated successfully, but these errors were encountered:
4. It depends on `kitinerary` (not to be confused with Itinerary!) which needs private headers from poppler to build. Poppler is a Jolla-supplied package and therefore can not be in Chum. The Jolla package does not package the private headers.
it is OK to add missing dependencies. we have done the same for other apps
I don't know much about KPIM5, maybe @piggz can comment. point for opt- was to distinguish from the apps using regular Qt from /usr/lib. if it requires separate opt-kpim5- then its ok. but I hope @piggz will know the case better.
it is OK to add them. maybe we will later add other apps using these libs
hmm, not sure how to do that. hopefully PR will be accepted, but it will take some time to be released (new SFOS release?).
Hi,
I have packaged "KDE Itinerary", a KDE/Kirigami application for Trip planning (it's similar to KTrip which already is in Chum).
See: https://apps.kde.org/itinerary/ for features.
My packaging project on OBS is this:
https://build.sailfishos.org/project/show/home:nephros:devel:qt515:itinerary
I would like to add it to the Chum Qt5/KF5 list of applications, HOWEVER there are a couple of things which might preclude that:
opt-kpim-foo
)?kf5-kcalendarcore
andkf5-kcontacts
; these compile fine, can be used as build deps, but of course are not useful on SFOS. Is that ok?kitinerary
(not to be confused with Itinerary!) which needs private headers from poppler to build. Poppler is a Jolla-supplied package and therefore can not be in Chum. The Jolla package does not package the private headers.The text was updated successfully, but these errors were encountered: