From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: "Koehler, Yannick" <yannick.koehler@hpe.com>,
"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: externalsrc + sstate why is not compatible?
Date: Wed, 6 Dec 2017 19:27:56 +0200 [thread overview]
Message-ID: <6f4e07a8-02f8-eac0-5d63-a6bf0ea42328@linux.intel.com> (raw)
In-Reply-To: <CS1PR8401MB08404303F44A38D6603DE3B3ED320@CS1PR8401MB0840.NAMPRD84.PROD.OUTLOOK.COM>
On 12/06/2017 04:13 PM, Koehler, Yannick wrote:
> When you say "subdirs", are you referring to submodules or something along those line? We have used attempted to use submodules and it still required 20 + 1 repo and the overhead is similar to yocto + 20 repo but then you have yocto + 20 repos + 1 main repos, as such, this is not acceptable for us. We also looked at other combination of multiple repos supported or in work for git and none are satisfying or supported in a way I could propose to use it in our project.
>
> If you mean 1 repo, which subdirs representing each package, I would be interested, but how would it work with yocto SRC_URI?
The latter. It's simple: you set SRC_URI in each recipe to the same
value, but set S differently:
S = "${WORKDIR}/git/module-1"
S = "${WORKDIR}/git/module-2"
etc.
Alex
prev parent reply other threads:[~2017-12-06 17:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-06 2:15 externalsrc + sstate why is not compatible? Koehler, Yannick
2017-12-06 8:47 ` Alexander Kanavin
2017-12-06 14:13 ` Koehler, Yannick
2017-12-06 14:47 ` Marcelo E. Magallon
2017-12-06 16:59 ` Koehler, Yannick
2017-12-06 18:45 ` Marcelo E. Magallon
2017-12-06 18:51 ` Koehler, Yannick
2017-12-06 17:27 ` Alexander Kanavin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6f4e07a8-02f8-eac0-5d63-a6bf0ea42328@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=yannick.koehler@hpe.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.