Re: [DISCUSSION] Issues, ToDo and Roadmap

[Baurzhan Ismagulov <ibr@radix50.net>]

On Tue, Feb 12, 2019 at 10:12:09AM +0100, Claudius Heine wrote:
> > > The github issue tracker of Isar is in a very sorry state. Some of
> > > those open issues are no longer applicable or already fixed. Maybe
> > > we could reactivate that and have some more moderators to keep that
> > > up to date?

FWIW, the issue tracker is good as a TODO list. The ML is good for discussions.
I'd like to keep both.

I agree that the tracker needs more attention. Maxim will look at that.

OTOH, maintaining != closing ASAP. The OP should get a response, but I don't
see a problem in having an issue for a long time if we want to have in Isar.


> Close #10 Allow cross-build for selected packages
> Close #21 Add support for package version pinning (fixed AFAIK,
> DISTRO_APT_PREFERENCES)

If that works and is documented.


> 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
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?


> Close #12 qemu: init 0 doesn't exit with qemuarm-jessie (WONTFIX, not sure
> why that is a isar issue)

That is an interesting perspective, thanks. Formulated in this way, I have to
agree :) . I've seen that in a way that Isar provides stuff that works and
tracks upstream issues just like Debian. So, in general, my approach would be
at least to report that upstream before closing here.

In this particular case, I doubt this is going to be fixed in jessie, so if
that works with stretch, we could close that.


> Close #14 bitbake: Multiconfig builds seem to be serialized (if that is
> still true, then that is a bitbake issue and needs to be fixed there not in
> isar)

Yes, fix in bitbake. Affects Isar -- TODO here.


> Close #15 Support AUTOREV in SRCREV (WONTFIX, that is a feature issue that
> is open for 1.5 years with no update, there seem to be no interest for this)

But would it be useful if it existed? My answer is yes. So what is the problem
with having a wishlist?


> Close #16 Jessie: Host configuration leakage around apt-get (WONTFIX, we
> don't use multistrap anymore)
> Close #17 wic does not find mkdosfs (FIXED, as commented by Henning half a
> year ago)
> Close #20 Override DISTRO_APT_SOURCE in local.conf? (no longer applicable
> AFAIK we now have DISTRO_APT_PREMIRRORS)

Thanks, closed.


> Close #18 IMAGE_TYPE = "wic" (FIXED, as commented by Henning half a year
> ago)

Stated with a question mark -- could anyone verify?


> Close or Update #19 Consider testing with http_proxy

Should be done in CI.


> Close #27 bitbake: Consider reading bitbake's and project's config (fixed
> AFAIK, we don't use the bitbake.conf from bitbake but have our own)
> Close #28 Document bitbake.conf concatenation (fixed AFAIK, since we don't
> concatenate anymore)

Project-specific bitbake.conf from scratch is the way described in the bitbake
docs [1] and was implemented by Isar in the beginning. Inheritable bitbake.conf
was suggested later; I am personally not sure what the value is. I've closed
that.


References

1. https://www.yoctoproject.org/docs/1.6/bitbake-user-manual/bitbake-user-manual.html#the-hello-world-example


With kind regards,
Baurzhan.