Skip to content

Create WPEFramework_boot.service - #11

Open
fzahir786 wants to merge 1 commit into
developfrom
topic/NOJIRA-4444
Open

Create WPEFramework_boot.service#11
fzahir786 wants to merge 1 commit into
developfrom
topic/NOJIRA-4444

Conversation

@fzahir786

Copy link
Copy Markdown
Owner

No description provided.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds a new systemd oneshot unit intended to run a WPEFramework “boot” plugin activation step as part of the WPEFramework startup flow.

Changes:

  • Introduces WPEFramework_boot.service as a oneshot unit that runs PluginActivator org.rdk.boot.
  • Adds dependency declarations and a ConditionPathExists=/tmp/wpeframeworkstarted gate.

[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/usr/bin/PluginActivator org.rdk.boot

Copilot AI Feb 19, 2026

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This unit currently has no [Install] section and there are no references to WPEFramework_boot.service elsewhere in the repo, so it won’t be started unless something external enables it or adds it as a dependency. Please either add proper boot integration ([Install] / WantedBy=) or ensure it’s pulled in by an existing target/path unit used to start WPEFramework plugin initializer services.

Refer: https://github.com/fzahir786/thunder-startup-services/blob/develop/.github/copilot-instructions.md#9-boot-integration-requirement

Suggested change
ExecStart=/usr/bin/PluginActivator org.rdk.boot
ExecStart=/usr/bin/PluginActivator org.rdk.boot
[Install]
WantedBy=multi-user.target

Copilot uses AI. Check for mistakes.
Comment on lines +1 to +2
[Unit]
Description=WPEFramework boot Initialiser

Copilot AI Feb 19, 2026

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The unit filename and implied unit name use mixed/upper casing (WPEFramework_boot.service) while the other WPEFramework-related unit files in systemd/system/ are consistently lowercase (wpeframework-*.service). Consider renaming this unit to match the established naming pattern to avoid confusion and reduce the chance of missing it in scripts/tooling that assume lowercase names.

Copilot uses AI. Check for mistakes.
@@ -0,0 +1,8 @@
[Unit]
Description=WPEFramework boot Initialiser
Requires=wpeframework.service wpeframework-persistentstore.service wpeframework-system.service wpeframework-deviceinfo.service

Copilot AI Feb 19, 2026

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Requires= does not enforce startup ordering; without a matching After= this unit may start before its prerequisites and then get skipped by ConditionPathExists (or fail if dependencies aren’t ready). This repo’s WPEFramework plugin initializer units consistently pair Requires= with After= for the same services (e.g., systemd/system/wpeframework-deviceinfo.service:3-4). Please add an After= line mirroring the required units.

Refer: https://github.com/fzahir786/thunder-startup-services/blob/develop/.github/instructions/Dependency_management.instructions.md#dependency-management-guidenlines

Suggested change
Requires=wpeframework.service wpeframework-persistentstore.service wpeframework-system.service wpeframework-deviceinfo.service
Requires=wpeframework.service wpeframework-persistentstore.service wpeframework-system.service wpeframework-deviceinfo.service
After=wpeframework.service wpeframework-persistentstore.service wpeframework-system.service wpeframework-deviceinfo.service

Copilot uses AI. Check for mistakes.
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.

2 participants