| *** zbenjamin is now known as Guest21761 | 01:04 | |
| *** zbenjamin_ is now known as zbenjamin | 01:04 | |
| useretail | just updated the software and got black screen. how to solve? | 01:42 |
|---|---|---|
| useretail | pkcon remove phonehook | 02:13 |
| useretail | also had screencast installed, but during version --dup update was failing because it couldn't remove screencast 0.3.0-10.18.1.jolla properly | 02:15 |
| useretail | Error: Subprocess failed. Error: RPM failed: /var/tmp/rpm-tmp.t8BDKB: line 1: fg: no job control | 02:15 |
| useretail | /var/tmp/rpm-tmp.t8BDKB: line 2: fg: no job control | 02:15 |
| useretail | error: %preun(screencast-0.3.0-10.18.1.jolla.armv7hl) scriptlet failed, exit status 1 | 02:15 |
| useretail | error: screencast-0.3.0-10.18.1.jolla.armv7hl: erase failed | 02:15 |
| useretail | UPGRADE NOT COMPLETE - Retry 1 of 9 | 02:16 |
| useretail | coderus, just fyi | 02:16 |
| gangadhar | A question on licensing when using the QtCreator for SF development. As per the Qt licensing terms, everyone using the Qt libraries has to call out upfront (during installation) whether they are an OSS developer or a commercial s/w developer | 02:48 |
| gangadhar | And there are separate licensing for both in Qt | 02:48 |
| gangadhar | If I want to develop a closed-source application in SFOS, I am using QML and C++ underneath, then can I build a closed-source application? What are the licensing terms I should be aware of? | 02:49 |
| *** frinring_ is now known as frinring | 03:36 | |
| gangadhar | All - any details about the closed-source development using Qt libraries for Sailfish? | 08:42 |
| gangadhar | I found this reference [ https://together.jolla.com/question/40495/qt-license-policy-and-paid-for-apps/ ] but this is for applications that are paid for on the store | 08:43 |
| gangadhar | Does the answered response for the above mean that as long as I am using Qt libs in my SFOS app dynamically I can keep my app-code closed-source and release it under a proprietary license? | 08:45 |
| mpol | current Qt on SFOS is mostly LGPL, which is fine for proprietary apps. For a proprietary app you cannot use GPL libraries. An update for Qt, like from 5.9 to 5.15, would possibly go GPL | 08:49 |
| gangadhar | Thanks mpol for that. I was looking for how the licensing changes if SFOS upgrades their Qt version in the future. Qt6 is expected to be released EoY and the static-typing in QML will be a great benefit for everyone | 08:59 |
| gangadhar | Is there a page on the WiKi that explains the licensing ? | 09:00 |
| mpol | that very much depends if they go with the GPL version or the commercial version. | 09:00 |
| gangadhar | If they went with GPL version - then a lot of app developers might be wary of it isn't it? If they link dynamically to Qt libraries then I think they should be ok (I think - please correct me if I am wrong) | 09:01 |
| gangadhar | Wouldn't it help to have a Wiki article for this bit ? | 09:01 |
| mpol | about licensing and linking to LGPL and GPL< the FSF has that explained. | 09:03 |
| mpol | https://www.qt.io/product/features Here you can see what is under GPL in the free software version and what is commercial | 09:04 |
| mpol | https://www.gnu.org/licenses/gpl-faq.html | 09:05 |
| gangadhar | Yes, mpol , the Qt license page, I am aware of. I meant a wiki page on SFOS | 09:18 |
| mpol | what would you want them to explain? They have not made public if, when and how they want to continue on the Qt update | 09:18 |
| gangadhar | For instance if one wants to only use LGPL-V3 [ https://www.qt.io/product/features#js-6-3 ], then even QtCreator is not available | 09:19 |
| gangadhar | I meant, having a page that details the different Qt versions and what the licensing options are available for developers. The above link maynot be relevant for Qt 5.9. I am trying to look for the licensing for Qt 5.9. | 09:20 |
| gangadhar | Found it - https://doc.qt.io/qt-5.9/licenses-used-in-qt.html | 09:20 |
| gangadhar | But it doesn't mention the license of Qt-Creator; would you know ? | 09:21 |
| mpol | be aware, I am not an app developer :) But the currently used qt-creator is part of the sdk, and I would think you can use proprietary apps with it, otherwise Jolla would not be able to do that as well. You might want to download the SDK and check the license | 09:26 |
| gangadhar | Sure mpol :) I am trying to understand that. In the SFOS SDK _Licenses_ folder, there are some explanations (including a LGPL_Exception file). Was thinking if someone in SFOS could make it simpler on Wiki so that app-developers are making the right choices | 09:30 |
| gangadhar | am sure that Jolla Inc has done their due diligence, but given that Qt license has been changing (including the recently added independent-developer license and the per-unit-deployed license), knowing the implications of using Qt for SFOS will help developers | 09:32 |
| gangadhar | I am not aware of the Jolla team members on this channel; should I send it as a forum post ? | 09:32 |
| mpol | afaik, and that might be too simple, for proprietary apps you cannot link to GPL software. And yes, the forum might be much better for this. The developer meetings are good to follow too | 09:33 |
| tmynttin | is there any way to kill crashed native apps other than from terminal? | 10:12 |
| tmynttin | my browser sometimes crashes and cannot be started unless killed from terminal | 10:13 |
| tmynttin | for android apps there is this 'Force stop' option in settings | 10:14 |
| kirvesAxe | tmynttin, install Crest from Jolla store... It shows you a list of open processes and a long press on a process name gives you options for terminate and force kill :) (I once had an issue that I needed to kill my crashed terminal, and I was working on something that I wanted to finish before rebooting...) | 11:28 |
| kirvesAxe | (You might need to open the top menu and change the setting of "Apps only") | 11:29 |
| tmynttin | kirvesAxe: great tip, thanks! | 11:38 |
| *** haasn` is now known as haasn | 21:29 | |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!