From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users@googlegroups.com
Subject: Re: Discussion: Base-apt features
Date: Wed, 25 Sep 2019 14:29:51 +0200 [thread overview]
Message-ID: <a30ff798-f2a5-24c1-1623-6ee703b7f229@siemens.com> (raw)
In-Reply-To: <20190925121922.43kgzt52pmcgkaui@yssyq.m.ilbers.de>
On 25.09.19 14:19, Baurzhan Ismagulov wrote:
> On Wed, Sep 25, 2019 at 01:56:37PM +0200, Claudius Heine wrote:
>>>>> 2. Support for using password protected keys.
>> Right. It would just be inconvenient to switch between those
>> configurations for the different use cases that should be satisfiable
>> simultaneously without change of configuration files or deleting build
>> results.
>>
>> I am currently not using Isar, but is something like this possible?
>>
>> BASE_REPO_KEY = "" bitbake ...
>> BASE_REPO_KEY = "prod.key" bitbake ...
>
> That would be indeed convenient. We could look whether bitbake supports that.
>
It's there some env-variable whitelisting for such scenarios?
Jan
>
>>>>> 4. Support for adding packages only to base-apt.
>>
>> Two departments of the same company, one that develops debian bin and
>> possible src packages and deploys them to a internal repo for other
>> departments to use, and the other department that takes these packages
>> and installs them to an image for the customer. Those packages are not
>> build by isar then and would be placed in the base-apt repo together
>> with the src package for delivery to the end-customer, which might not
>> be what was desired.
>>
>> We should probably just check the license and only deliver packages that
>> are required to be redistributed.
>
> Thanks for the scenario, we could consider covering this in some way.
>
>
> With kind regards,
> Baurzhan.
>
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2019-09-25 12:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-25 7:41 Vijai Kumar K
2019-09-25 8:12 ` Baurzhan Ismagulov
2019-09-25 9:02 ` Vijai Kumar K
2019-09-25 9:51 ` Baurzhan Ismagulov
2019-09-25 10:14 ` Claudius Heine
2019-09-25 10:26 ` Baurzhan Ismagulov
2019-09-25 11:56 ` Claudius Heine
2019-09-25 12:19 ` Baurzhan Ismagulov
2019-09-25 12:29 ` Jan Kiszka [this message]
2019-09-25 12:39 ` Claudius Heine
2019-09-26 9:40 ` Henning Schild
2019-09-26 11:02 ` Vijai Kumar K
2019-09-26 11:30 ` Henning Schild
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=a30ff798-f2a5-24c1-1623-6ee703b7f229@siemens.com \
--to=jan.kiszka@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