Fix the gbs export doesn't generate patches when packaging non-native package. 62/299962/2
authorwanchao-xu <wanchao.xu@samsung.com>
Fri, 13 Oct 2023 01:43:36 +0000 (09:43 +0800)
committerwanchao-xu <wanchao.xu@samsung.com>
Fri, 13 Oct 2023 02:24:53 +0000 (10:24 +0800)
commitbdf38d8023f89ef48d75ed3cb4430e09e0f447d4
tree1ddbc7cec8532fa5bfd57611e1b53daed876ebfc
parent7273cdc733bc22e04d0a7aeba2bc17f00dbe28ea
Fix the gbs export doesn't generate patches when packaging non-native package.

Reason:
The packages can be divided into 2 categories: native packages and non-native (or upstream) packages.
Please refer to https://docs.tizen.org/platform/reference/gbs/gbs-maintenance-models/.
If the package has export branch and upstream branch, but the export branch is not based on upstream,
gbs will export this package as no-native without auto-generate patches.

Solution:
Export the package as native package if the export branch is not based on upstream.

Change-Id: I16f12acc9ab2111f8f5b2e966bbf6b4d56ae5086
Signed-off-by: wanchao-xu <wanchao.xu@samsung.com>
gitbuildsys/cmd_export.py