public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [DISCUSSION] Issues, ToDo and Roadmap
Date: Tue, 12 Feb 2019 13:05:51 +0100	[thread overview]
Message-ID: <3d07d2c5-b7a2-5694-6ff9-1c35171eb039@siemens.com> (raw)
In-Reply-To: <20190212111711.GH805@yssyq.m.ilbers.de>

On 12.02.19 12:17, Baurzhan Ismagulov wrote:
>> Close #11 Enable non-root building (WONTFIX, I don't see that happening
>> anytime soon)
> 
> We have a stale PoC implementation. If Yocto does it, it should be possible. It

Yocto is not comparable to normal distro installation, that's why Debian folks 
were skeptical as well - "maintainability" is the key.

> might not be the highest priority ATM, but it would be nice to have. Maybe
> someone seeing it would have enough itch do do that. Otherwise, how do you
> suggest to communicate the roadmap you are talking about?
> 

The POC should ideally be linked in the issue. At least a status update would be 
good. I'm also missing links to follow-up discussion we had, e.g. around binfmt. 
Not sure anymore, though, if they were on the public list.

Jan

  reply	other threads:[~2019-02-12 12:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-11 10:19 Claudius Heine
2019-02-11 12:50 ` Jan Kiszka
2019-02-11 15:21 ` Maxim Yu. Osipov
2019-02-12  9:12   ` Claudius Heine
2019-02-12 11:17     ` Baurzhan Ismagulov
2019-02-12 12:05       ` Jan Kiszka [this message]
2019-02-12 12:18       ` Claudius Heine
2019-02-12 12:40       ` Henning Schild
2019-02-12 14:41         ` 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=3d07d2c5-b7a2-5694-6ff9-1c35171eb039@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