RDKEVD-1128 : MW ipk feedpath

[aktamilbe]

No description provided.

[Copilot]

Pull request overview

Updates the middleware OPKG feed configuration to pull IPKs from a different artifacts sub-path and to use a new middleware release identifier.

Changes:

• Switches middleware feed root from middleware-rel/${RELEASE_NUM} to middleware-dbg/${RELEASE_NUM} for both standard and OSS middleware feeds.
• Updates RELEASE_NUM to DVCalibrationMW_1.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
conf/machine/include/oss_mw.inc	Updates OSS middleware IPK feed path root to middleware-dbg/${RELEASE_NUM}.
conf/machine/include/middleware.inc	Updates RELEASE_NUM and switches middleware IPK feed path root to middleware-dbg/${RELEASE_NUM}.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated no new comments.

Comments suppressed due to low confidence (2)

conf/machine/include/middleware.inc:8

• RELEASE_NUM is set with a strong assignment (=), which makes it harder for downstream configuration (e.g., distro/local.conf) to supply a different release without relying on parse-order overrides. Since this include file appears to provide defaults, use a weak assignment (?=) to make the release identifier easily configurable.

RELEASE_NUM = "DVCalibrationMW_3"

conf/machine/include/oss_mw.inc:6

• MW_OSS_IPK_SERVER_PATH uses a strong assignment (=), which makes it less configurable than the non-OSS equivalent (MW_IPK_SERVER_PATH ?= in middleware.inc). If this is intended as a default feed URL, consider switching to ?= so downstream builds can override it cleanly without depending on parse order.

MW_OSS_IPK_PATH ?= "middleware-dbg/${RELEASE_NUM}"
MW_OSS_IPK_SERVER_PATH = "${RDK_ARTIFACTS_BASE_URL}/${MW_OSS_IPK_PATH}/${RDK_MW_ARCH}/${MW_OSS}/ipks/${BUILD_VARIANT}"