Hi,
I'm trying to reuse the manifest <include>. It works well for an <include> manifest that includes a second child manifest for particular software components (SWC).
I'm providing a generalized example, but I hope this gets the point across without requiring the exact manifest file syntax for the example.
Manifest SWC_Target ->
<include name="SWC1"/> ->
<include name="SWC3"/>
However, I'm trying to handle the scenario when I have 2 different <include> under SWC_Target that both have a dependencies pointing to the same dependent SWC.
Manifest SWC_Target ->
<include name="SWC1"/> ->
<include name="SWC3"/>
<include name="SWC2"/> ->
<include name="SWC3"/>
If I have to repo sync SWC1 and SWC2 independently it is successful. However, currently, if I repo sync SWC_Target then it will complain that there is a duplicate.
error: in `sync -m swc/includetest.manifest.xml`: duplicate path src/SWC3 in /random/swc-test/.repo/manifests/swc/includetest.manifest.xml
Is there anyway to tell repo tool to ignore <include> conflicts or get it to not complain if conflict's dependency <project> values for name, path and revision are the same?
Please let me know if this is a new feature request.
========
repo --version
... A new version of repo (2.50) is available.
... You should upgrade soon:
cp /opt/code/swc-is-jsoncpp/.repo/repo/repo /home/randomuser/.bin/repo
repo version v2.52
(from
https://gerrit.googlesource.com/git-repo)
(tracking refs/heads/stable)
(Wed, 5 Feb 2025 12:36:27 -0800)
repo launcher version 2.45
(from /home/randomuser/.bin/repo)
(currently at 2.52)
repo User-Agent git-repo/2.52 (Linux) git/2.7.4 Python/3.6.10
git 2.7.4
git User-Agent git/2.7.4 (Linux) git-repo/2.52
Python 3.6.10 (default, Dec 19 2019, 23:04:32)
[GCC 5.4.0 20160609]
OS Linux 4.4.0-87-generic (#110-Ubuntu SMP Tue Jul 18 12:55:35 UTC 2017)
CPU x86_64 (x86_64)
========
Thank you for your time to read this.