-
Notifications
You must be signed in to change notification settings - Fork 445
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add QT extension #4294
base: main
Are you sure you want to change the base?
Add QT extension #4294
Conversation
6843f00
to
3b07cab
Compare
3b07cab
to
a4c401f
Compare
f9b8cdb
to
d52c124
Compare
Codecov ReportAttention:
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## main #4294 +/- ##
==========================================
- Coverage 89.19% 88.35% -0.85%
==========================================
Files 322 328 +6
Lines 21826 22035 +209
==========================================
+ Hits 19468 19469 +1
- Misses 2358 2566 +208 ☔ View full report in Codecov by Sentry. |
d52c124
to
bac174a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, nice work!
Can you create a spread test for 5.15 and 6.5 under tests/spread/extensions/
? You can use the other spread tests in that directory as a reference.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Update for anyone watching:
This PR is waiting on @jardon getting auto-connect approvals for the two qt-framework
snaps used by this extension
Store request submitted here |
you store request has updates |
The CI can be rerun when the snapcraft forum post is resolved. |
@sergiusens @mr-cal do you know where snapctl is getting the
|
@mr-cal Can I get the CI kicked back off? |
I updated the content snaps to correct the plug check issue |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #4294 +/- ##
==========================================
+ Coverage 88.35% 88.38% +0.02%
==========================================
Files 328 329 +1
Lines 22015 22088 +73
==========================================
+ Hits 19452 19523 +71
- Misses 2563 2565 +2 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FYI @cmatsuoka, jardon is no longer at Canonical, so I don't think any progress is being made on this. We need to decide what to do with his qt-framework
content snaps and this PR.
that is more or less correct. this has been demoted in priority for me, but that doesnt mean that i cant work to get this pushed through. there are a couple of reasons that i havent worked on this in quite a while. firstly, building and maintaining the sdk and content snaps is unfortunately too big of a burden. i cant build the images in github actions because of resource limitations as well as architecture. yes, theres launchpad, but a new coat of paint doesnt mean its basically abandonware (seriously stand up a gitlab instance and convert all the useful bits of launchpad into a plugin or something). secondly, the current snap architecture increases the amount of work beyond whats reasonable. having to have separate snaps for each combination of QT version and base, dealing with the annoyances of the content interface, as well as dealing with store requests makes this a lot to maintain. if you can offer good solutions to my issues above, i'd be happy to help. |
|
||
_SDK_SNAP = {"core22": "qt-framework-sdk"} | ||
|
||
_CONTENT_SNAP = { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Who owns these snaps?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
that would be me.
For some more context here, I originally wanted to partner with the KDE snap people for creating snaps that would be the building blocks for both extensions. Unfortunately, it seems they got busy with the KDE Ubuntu spin and never responded which is another reason why this stalled. |
Any update on this? |
@keshavbhatt i have not heard back from canonical |
Hi @keshavbhatt, we haven't decided on how to proceed with the QT extension and content snaps. |
make lint
?pytest tests/unit
?This PR adds support for two QT extensions (6.5 and 5.15)