From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Subject: Re: Discussion: Base-apt features
Date: Wed, 25 Sep 2019 12:26:07 +0200 [thread overview]
Message-ID: <20190925102607.cpvf6wurb4orwigx@yssyq.m.ilbers.de> (raw)
In-Reply-To: <d402e690-3dbb-72c7-d0f4-3043ddca6762@denx.de>
Hello Claudius,
On Wed, Sep 25, 2019 at 12:14:19PM +0200, Claudius Heine wrote:
> > 2. Support for using password protected keys.
>
> There are two use-cases for base-apt AFAIK: Use it to distribute a
> repository to the end user and for reproducible/offline build.
>
> I agree that for the former having a password protected key for signing
> the repo would be good. For the latter use-case though that might get
> cumbersome.
>
> Maybe we should split this use-case and have something different for
> reproducible/offline build?
This is my understanding. I see all of the following as required:
1. Unsgined base-apt
2. Signed base-apt w/o passphrase
3. Signed base-apt w/passphrase
> Also 'base-apt' is a bad name...
Like with isar-apt, it was difficult to find a short and intuitive one. Do you
have a suggestion?
> > 4. Support for adding packages only to base-apt.
>
> If the base-apt should be used for distributing packages to the
> end-user, it might also be useful to exclude certain packages.
Could you give an example? After that is a copy of Debian, what is your
concern?
With kind regards,
Baurzhan.
next prev parent reply other threads:[~2019-09-25 10:26 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 [this message]
2019-09-25 11:56 ` Claudius Heine
2019-09-25 12:19 ` Baurzhan Ismagulov
2019-09-25 12:29 ` Jan Kiszka
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=20190925102607.cpvf6wurb4orwigx@yssyq.m.ilbers.de \
--to=ibr@radix50.net \
--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