Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR seeks to provide the implementation of a flatpak-based demo installer for eSim (WIP⚠️ )
where the following actions are possible :
Approach
The demo application executes the various operations with the following methods:
The installed package method, install_Pip_package(self):
Installs a selected package using pip. It uses a subprocess to check_call system commands and outputs results to a QPlainTextEdit.
The Verilator installation method, intall_Verilator_from_Archive(self):
Installs Verilator from a 7-zip archive file using a system pkexec command. The method extracts files from the archive and moves them to /usr/bin/. It uses a subprocess to check_call system commands and outputs results to a QPlainTextEdit.
The method install_Verilator_SRC(self) installs Verilator from the source:
It triggers a separate thread, InstallThread_SRC(QThread), which executes a shell script containing commands to download the source files and install Verilator. It uses subprocess run and print statements to track the progress of the installation. The thread sends progress updates to the main thread where it is used to update a QPlainTextEdit.
How does this address the problem?
The application is Packaged as a flatpak, which requires the runtime
org.kde.Sdk
version5.15-22.08
and the SDKorg.kde.Sdk
. It is based on thecom.riverbankcomputing.PyQt.BaseApp
version5.15-22.08
.The application uses
org.kde.Sdk
as its runtime to provide various build tools, however, it can be later replaced byorg.kde.Platform
, and separate modules for additional build tools likegit, make, autoconf, etc...
can be added to the manifest.The application's default permissions are specified in its Flatpak Manifest
"org.flatpak.FOSSEE_Inst_test.yml"
, including sharing Inter-Process Communication and network access, an X11 and Wayland socket, access to the host OS filesystem and home directory, DRI device access, and a "talk name" for communication over D-Bus.