Re: KCGroups in KDEreview
> > (where 1000 is of course dynamic) > > Ditto, what enum names could we give to those? / -> All /system.slice -> System user.slice/user-1000.slice/user@1000.service -> User user.slice/user-1000.slice/user@1000.service/app.slice -> UserApps user.slice/user-1000.slice/user@1000.service/session.slice -> UserSession user.slice/user-1000.slice/user@1000.service/background.slice -> UserBackground > Yes, I know I roll with questions. :-) > Cheers. > -- > Kevin Ottens, http://ervin.ipsquad.net
Re: KCGroups in KDEreview
Hello, On Tuesday, 2 March 2021 12:06:51 CET David Edmundson wrote: > > > (where 1000 is of course dynamic) > > > > Ditto, what enum names could we give to those? > > / -> All > /system.slice -> System > user.slice/user-1000.slice/user@1000.service -> User > user.slice/user-1000.slice/user@1000.service/app.slice -> UserApps > user.slice/user-1000.slice/user@1000.service/session.slice -> UserSession > user.slice/user-1000.slice/user@1000.service/background.slice -> > UserBackground Sounds good to me. Let's go for this. Regards. -- Kevin Ottens, http://ervin.ipsquad.net enioka Haute Couture - proud patron of KDE, https://hc.enioka.com/en signature.asc Description: This is a digitally signed message part.
KDE Gear releases & Frameworks dependencies
Hi, for the KDE Gear release service releases, what is actually an acceptable Frameworks release requirement for the upcoming 21.04? e.g. at the moment, Kate requires Frameworks 5.79 in master, we needed some new API to avoid ugly hacks. Would it be acceptable to move this to the latest version that will be out in March, e.g. 5.80? Or will this lead to issues? That way we (the Kate people) could ensure that Kate 21.04 will only be (without that people patch it) build-able against some Frameworks release that has at least the bugs fixed that we really care about. Greetings Christoph -- Ignorance is bliss... https://cullmann.io | https://kate-editor.org
Re: KDE Gear releases & Frameworks dependencies
El dimarts, 2 de març de 2021, a les 19:39:57 CET, Christoph Cullmann va escriure: > Hi, > > for the KDE Gear release service releases, what is actually an > acceptable Frameworks release requirement for the upcoming 21.04? > > e.g. at the moment, Kate requires Frameworks 5.79 in master, we needed > some new API to avoid ugly hacks. > > Would it be acceptable to move this to the latest version that will be > out in March, e.g. 5.80? > > Or will this lead to issues? Applications and libraries part of the release service can define their own dependencies, the worst that can happen is that your application doesn't get packaged for some distributions because your dependency is un-attainable for them, but that's a risk you seem be willing to take, so nothing against it. On the other hand from a release point of view, the release service dependency freeze is on March 11 and KDE Frameworks 5.80 is not released until March 13, so I would personally prefer you don't do that. It's very possible that I won't have KDE Frameworks 5.80 avaialble for me when doing the Beta release on March 18. Is it really that needed to have that KF5 version for kate? Are the features enabled by that KF5 version so critical they can't wait for 21.08 or maybe be protected with ifdefs? Cheers, Albert > > That way we (the Kate people) could ensure that Kate 21.04 will only be > (without that people patch it) > build-able against some Frameworks release that has at least the bugs > fixed that we really care about. > > Greetings > Christoph > >
Re: KDE Gear releases & Frameworks dependencies
On 2021-03-02 22:11, Albert Astals Cid wrote: El dimarts, 2 de març de 2021, a les 19:39:57 CET, Christoph Cullmann va escriure: Hi, for the KDE Gear release service releases, what is actually an acceptable Frameworks release requirement for the upcoming 21.04? e.g. at the moment, Kate requires Frameworks 5.79 in master, we needed some new API to avoid ugly hacks. Would it be acceptable to move this to the latest version that will be out in March, e.g. 5.80? Or will this lead to issues? Applications and libraries part of the release service can define their own dependencies, the worst that can happen is that your application doesn't get packaged for some distributions because your dependency is un-attainable for them, but that's a risk you seem be willing to take, so nothing against it. On the other hand from a release point of view, the release service dependency freeze is on March 11 and KDE Frameworks 5.80 is not released until March 13, so I would personally prefer you don't do that. It's very possible that I won't have KDE Frameworks 5.80 avaialble for me when doing the Beta release on March 18. Is it really that needed to have that KF5 version for kate? Are the features enabled by that KF5 version so critical they can't wait for 21.08 or maybe be protected with ifdefs? No, 5.80 isn't needed. Just wanted to ask how the general feeling is for such things. 5.79 makes the life a lot easier and I see no problem with that, given with old frameworks you have bugs you don't to have with the 21.04 release, can live with it not being packaged on such systems. Will just stick with 5.79, thanks for the feedback! Greetings Christoph Cheers, Albert That way we (the Kate people) could ensure that Kate 21.04 will only be (without that people patch it) build-able against some Frameworks release that has at least the bugs fixed that we really care about. Greetings Christoph -- Ignorance is bliss... https://cullmann.io | https://kate-editor.org
