- User Since
- Apr 18 2015, 1:59 PM (242 w, 5 d)
Mon, Dec 9
Looks good, thanks. We do that this way: apply to branch 3.2 and then merge 3.2 into master. Please ask if unsure.
Sun, Nov 24
Nov 4 2019
Nov 1 2019
Oct 31 2019
Oct 29 2019
Oct 10 2019
Sep 29 2019
Sep 15 2019
Aug 19 2019
May 28 2019
May 20 2019
Apr 23 2019
Apr 2 2019
Well I am not pushing for the cert, in fact it's hard to say how it would be seen by users: is KEXI widely certified and tested by KDE? No, no KDE app is, it's local work.
Maybe I'll have commercial certification or/and the app in app stores. Too early to say.
BTW is it possible to get KDE certificate for the installer?
Apr 1 2019
- KEXI: qtlocation and qtsensors are needed by Qt5WebKit, do not disable
Mar 26 2019
- KEXI: Use "explorer <link>" to Run KEXI per user request, under explorer's user
- KEXI: move files copying to preArchive()
- KEXI: Update package names, ignore also: kemoticons, kdesignerplugin, hunspell-dictionaries
Mar 25 2019
@vonreth Everything works as I expected now... I know, the fashion can be improved.
- KEXI: ignore hunspell and qtlocation/sensors/qqcontrols2
- Simplify blacklist for KEXI, ignore more files
- NSIS Installer for KEXI: Improve start menu and install dir removal (remove parent KEXI folder if makse sense), fix folder names
Mar 14 2019
Updated files, now the installer builds and works. "Run KEXI" from installer does not work and start menu location is not as I expected.
Mar 13 2019
Mar 12 2019
Mar 9 2019
Mar 8 2019
Mar 6 2019
Feb 20 2019
Feb 18 2019
Very good, by chance, where are the artifacts for kexi builds?
Feb 17 2019
Feb 12 2019
Feb 5 2019
Thanks a lot @apol, it looks promising and clean. I have questions based on my limited knowledge of these json files:
- kreport, kproperty, kdb modules - can their branch be 3.2 too? They're BC but still using stable dependencies for stable builds would be better
- the top level "branch" attribute is master, not sure what it means
- what would be the URL at https://binary-factory.kde.org/ for the stable?
Feb 1 2019
Right, for master and stable (currently "3.2").
Jan 30 2019
@apol Thanks, adding another nightly for other branch was my initial though. Can we add this? We would be done then.
Thanks Ben, it's hard to argue with this standard behavior. I am wondering though how to trigger the build in projects like KEXI - there can be weeks of development when changes are in kdb.git only and not in kexi.git. More precisely, how to deal with that without adding artificial commits to kexi.git.
Landed, now how to rebuild it? Can I get rights to click Rebuild?
I may want this in other cases, e.g. when kexi.git is unchanges but when dependencies changed and we want to test things while testers are waiting for binaries. For nightly builds it means one test per 24h I'd assume?
Yes, Ben summarized what I meant. Thanks. We're not yet there (that is, production-ready flatpack or app store of any kind, with QA and regular contributors). We can't have all of this the day one, we need nighties so would-be contributors who are not developers have the chances to test current software (stable/unstable). Current state is that many contributors (power users) run 1 or 2 years old software so even initial conversation within bugs.kde.org is problematic.