From: "Cirujano Cuesta, Silvano" <silvano.cirujano-cuesta@siemens.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Cc: "Wagner, Daniel" <daniel.wagner@siemens.com>,
"Schild, Henning" <henning.schild@siemens.com>
Subject: ISAR doesn't honor DL_DIR
Date: Tue, 27 Nov 2018 12:56:27 +0000 [thread overview]
Message-ID: <1543323384.28585.20.camel@siemens.com> (raw)
I'm moving here a discussion that I've inadvertently started in GitHub
with an issue: [1]
According to the Bitbake upstream documentation, the variable DL_DIR is
being honored. So I would expect ISAR to also honor it. But ISAR is not
honoring it in my setup.
Apparently Bitbake is honoring it in Yocto setups, meaning that Yocto
also honors it.
Is ISAR expected to honor it or not? Is it a bug in ISAR? Is it an
error in my setup?
Cheers,
Silvano
[1] https://github.com/ilbers/isar/issues/43
next reply other threads:[~2018-11-27 12:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 12:56 Cirujano Cuesta, Silvano [this message]
2018-11-27 13:27 ` Jan Kiszka
2018-11-27 14:46 ` Cirujano Cuesta, Silvano
2018-11-27 13:29 ` Baurzhan Ismagulov
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=1543323384.28585.20.camel@siemens.com \
--to=silvano.cirujano-cuesta@siemens.com \
--cc=daniel.wagner@siemens.com \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox