Skip to content

Add The Qt Company's family of Qt extensions #856

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

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

peat-psuwit
Copy link
Contributor

@peat-psuwit peat-psuwit commented Apr 16, 2025

  • I have read the note above about PRs contributing or fixing extensions
  • I have tried reaching out to the extension maintainers about publishing this extension to Open VSX (if not, please create an issue in the extension's repo using this template).
  • This extension has an OSI-approved OSS license (we don't accept proprietary extensions in this repository)

Description

This add The Qt Company's family of Qt extensions. PR These extensions all live in a single repository. Most extensions are relatively straight-forward to build (non-extension-pack ones require building common library first). However, qt-core comes with a binary written in Go, which requires us to use custom commands to facilitate building it using GoReleaser.

Build commands have handling for difference between the currently- published version and the current Git tip, in anticipation that the Git tip will eventually be released.

GitHub workflows are modified to ensure Go environment is available.

Extensions are dual-licensed between Qt's commercial license and LGPL 3.0 only. The issue which request publishing on Open-VSX [1] gets some interest from upstream, but does not have any update since September 2024.

[1]: https://bugreports.qt.io/browse/VSCODEEXT-96

These extensions all live in a single repository. Most extensions are
relatively straight-forward to build (non-extension-pack ones require
building common library first). However, qt-core comes with a binary
written in Go, which requires us to use custom commands to facilitate
building it using GoReleaser.

Build commands have handling for difference between the currently-
published version and the current Git tip, in anticipation that the Git
tip will eventually be released.

GitHub workflows are modified to ensure Go environment is available.

Extensions are dual-licensed between Qt's commercial license and LGPL
3.0 only. The issue which request publishing on Open-VSX [1] gets some
interest from upstream, but does not have any update since September
2024.

[1]: https://bugreports.qt.io/browse/VSCODEEXT-96

Signed-off-by: Ratchanan Srirattanamet <[email protected]>
@peat-psuwit
Copy link
Contributor Author

Note: I've actually add a re-ping comment to the aforementioned upstream issue. My intention is if there's no response from upstream by Thursday (a week after the comment), I would proceed to un-draft the PR.

@peat-psuwit
Copy link
Contributor Author

Upstream has shown an interest in uploading extensions to Open-VSX. I'll see if this will eventually happen, and if so will close this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant