public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Cirujano Cuesta, Silvano" <silvano.cirujano-cuesta@siemens.com>
To: "isar-users@googlegroups.com" <isar-users@googlegroups.com>,
	"Kiszka, Jan" <jan.kiszka@siemens.com>
Cc: "Wagner, Daniel" <daniel.wagner@siemens.com>,
	"Schild, Henning" <henning.schild@siemens.com>
Subject: Re: ISAR doesn't honor DL_DIR
Date: Tue, 27 Nov 2018 14:46:56 +0000	[thread overview]
Message-ID: <1543330014.18068.4.camel@siemens.com> (raw)
In-Reply-To: <361293cc-afe3-eed2-6946-b7d43fad9e69@siemens.com>

On Tue, 2018-11-27 at 14:27 +0100, Jan Kiszka wrote:
> On 27.11.18 13:56, [ext] Cirujano Cuesta, Silvano wrote:
> > 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?
> > 
> 
> Isar and Bitbake, but help might be on the way, see 
> https://groups.google.com/d/msgid/isar-users/840a2535ca72f3ff2c900b2c
> e111fa9f60c1ee84.camel%40denx.de
> 
> Jan
> 

What a timing!

Apparently I should have subscribed to the mailing list sooner. Now I'm
in ;-)

Silvano

--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

  reply	other threads:[~2018-11-27 14:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-27 12:56 Cirujano Cuesta, Silvano
2018-11-27 13:27 ` Jan Kiszka
2018-11-27 14:46   ` Cirujano Cuesta, Silvano [this message]
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=1543330014.18068.4.camel@siemens.com \
    --to=silvano.cirujano-cuesta@siemens.com \
    --cc=daniel.wagner@siemens.com \
    --cc=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.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