public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: "[ext] Claudius Heine" <claudius.heine.ext@siemens.com>,
	"Hosgor, Tolga (CT RDA DS EU TR MTS)" <tlghosgor@gmail.com>,
	isar-users@googlegroups.com
Subject: Re: [PATCH] isar-bootstrap: debootstrap --include flag to support https:// sources
Date: Tue, 4 Dec 2018 15:28:11 +0100	[thread overview]
Message-ID: <abcb0b66-388d-5f6f-2287-db588af816c8@siemens.com> (raw)
In-Reply-To: <a4f71605-e82a-75d0-ac1c-153156d939e4@siemens.com>

On 04.12.18 15:23, [ext] Claudius Heine wrote:
>> @@ -138,6 +154,12 @@ def get_distro_components_argument(d, is_host):
>>       else:
>>           return ""
>> +def get_debootstrap_includes(d, is_host=False):
>> +    if get_distro_have_https_source(d, is_host):
>> +        return "locales,apt-transport-https,ca-certificates"
> 
> Those package names should be configured in the distro config.
> 

Means you would suggest to introduce two variables, e.g. DEBOOTSTRAP_INCLUDE and 
DEBOOTSTRAP_INCLUDE_HTTPS to encode those packages? Those could then be set in 
distro confs and simply used here.

Jan

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

  reply	other threads:[~2018-12-04 14:28 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 [this message]
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
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=abcb0b66-388d-5f6f-2287-db588af816c8@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=claudius.heine.ext@siemens.com \
    --cc=isar-users@googlegroups.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