public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Claudius Heine <claudius.heine.ext@siemens.com>
To: "Jan Kiszka" <jan.kiszka@siemens.com>,
	"Tolga Hoşgör" <tlghosgor@gmail.com>
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH] isar-bootstrap: debootstrap --include flag to support https:// sources
Date: Wed, 5 Dec 2018 14:04:02 +0100	[thread overview]
Message-ID: <127b3b98-7288-9356-7fad-4fe1b4bad9a3@siemens.com> (raw)
In-Reply-To: <636386f3-7eca-10bd-1ea1-1d5286ce15a9@siemens.com>

Hi Jan,

On 05/12/2018 13.58, Jan Kiszka wrote:
> On 05.12.18 13:55, Claudius Heine wrote:
>> On 05/12/2018 13.27, [ext] Claudius Heine wrote:
>>>>
>>>> Now I am completely lost. I suppose there is no need to create the
>>>> logic to to differentiate HTTP and HTTPS in ISAR if distro conf will
>>>> set the packages. Distro configuration knows whether if it is using
>>>> HTTP or HTTPS (or in theory something else) and it should be enough to
>>>> define/extend _one_ variable accordingly.
>>>
>>> I would suggest calling those variables like this:
>>>
>>> DISTRO_BOOTSTRAP_BASE_PACKAGES = "locales"
>>> DISTRO_BOOTSTRAP_BASE_PACKAGES_append_https-support = " 
>>> apt-transport-https ca-certificates"
>>>
>>> # OVERRIDE = "...:https-support:..." # when you detect that https is 
>>> needed.
>>>
>>> or similar. And then use those variables in isar-bootstrap with your 
>>> logic.
>>
>> Maybe I should be a bit more explicit here.
>>
>> The distro config does *not* know if somewhere else (some other 
>> configuration, file potentially from another layer) adds an additional 
>> repository that uses https. Since isar-bootstrap already does some 
>> parsing of the source lists and calls debootstrap, it would be the 
>> right point to handle that.
> 
> Do we really need to model that with overrides? It brings some 
> complexity of its own when changing that dynamically.

Of course we don't *need* to. I just don't like introducing new 
variables all the time. At some point converging to some small set of 
variables is desirable. (IMO we have to many of them in isar as is)

IMO that is a trade-off and there is no right solution here. I just 
wanted to point that out that this might be possible and then let the 
person writing the patch decides.

Claudius

-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de

  reply	other threads:[~2018-12-05 13:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-04 13:35 Hosgor, Tolga (CT RDA DS EU TR MTS)
2018-12-04 14:11 ` Jan Kiszka
2018-12-04 14:23 ` Claudius Heine
2018-12-04 14:28   ` Jan Kiszka
2018-12-04 14:46     ` Claudius Heine
2018-12-05 10:28       ` Tolga Hoşgör
2018-12-05 12:27         ` Claudius Heine
2018-12-05 12:55           ` Claudius Heine
2018-12-05 12:58             ` Jan Kiszka
2018-12-05 13:04               ` Claudius Heine [this message]
2018-12-05 17:09           ` Henning Schild
2018-12-05 17:12 ` Henning Schild
2018-12-11  7:17 ` Henning Schild
2018-12-11 17:08   ` Tolga Hoşgör

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=127b3b98-7288-9356-7fad-4fe1b4bad9a3@siemens.com \
    --to=claudius.heine.ext@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.com \
    --cc=tlghosgor@gmail.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