From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6656685609396994048 X-Received: by 2002:a1c:96d2:: with SMTP id y201mr230805wmd.3.1549970233948; Tue, 12 Feb 2019 03:17:13 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a1c:e919:: with SMTP id q25ls338911wmc.6.gmail; Tue, 12 Feb 2019 03:17:13 -0800 (PST) X-Google-Smtp-Source: AHgI3IZqADK9RgHH2fROGObTl6YQfSP0bPSqcUTn0VJedOQHjCYZS/vVq0+GDILtaCGuMJ20i9SE X-Received: by 2002:a1c:23ca:: with SMTP id j193mr237774wmj.1.1549970233555; Tue, 12 Feb 2019 03:17:13 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1549970233; cv=none; d=google.com; s=arc-20160816; b=XrfLDa4cV5BpaDpi0FrqELGnoHgsk442V37EZFRy2zVlFU4nLgqwlPoYd4yYADqF6n Xfh3mLruRSPsEq3NZ954t7DUWYRPQ1XI9GJbtJZsAReLgopM9T7NRREU8WlHYNRFLtMC 7KjZYZB6DEC0R4UkakPgJec1q8Bdcz13ZRZrD8YcoHomnAI06UXAO+90AVxiYBCnrAOZ LZpWsvbcO6nP13LO+lxRH2GrtnNYL5y8x/csCnYvpmpruuVitozMyMq0cF4FB+eKuI3r qRBGz/+RYrADZetnoTmGcyWXSu/AwwUp7P9un1v7WTo9ruvLp1eczkO1x+FYi7FXSIbC QFKg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=user-agent:in-reply-to:content-disposition:mime-version:references :mail-followup-to:message-id:subject:to:from:date; bh=wknDcozJs9fRc75PBkovWmJRKFDjuaVRzAgO/up1EfM=; b=iAmcIg6x4XD5/OEKEJagkZhOQtZJXpLouhp3sXs5XRtPG3fToBRCiPNPUQJF0fRdC0 zwbZXzsDc6+JwuK93uNlezfYViFB89WIwvRwUQAf58ShkJXZhNoer6mrdsWJTN7OVv/Q 5Iuks+GmR/IQW5YfAz15RtL9yXDaWqkHiPAjC5Mq+Qxb8M/IYvJE5i03HfrZ6qXUbms+ 1WUoLY2yyrH3kQP3ljM7Fo9YDVgB6n1U+ZTvtlWkN4ICcDfCVs9eAcYXxIN/kdfHhfZq YCVyKlvHFH7gSrqWvVVPATu85HTeX4WBVJ5a+27177Y4UZBQztmKqm8n0OQT+d7owuUr iW3w== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=neutral (google.com: 85.214.156.166 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) smtp.mailfrom=ibr@radix50.net Return-Path: Received: from shymkent.ilbers.de (shymkent.ilbers.de. [85.214.156.166]) by gmr-mx.google.com with ESMTPS id y6si121334wmd.1.2019.02.12.03.17.13 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 12 Feb 2019 03:17:13 -0800 (PST) Received-SPF: neutral (google.com: 85.214.156.166 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) client-ip=85.214.156.166; Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: 85.214.156.166 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) smtp.mailfrom=ibr@radix50.net Received: from yssyq.m.ilbers.de (host-80-81-17-52.static.customer.m-online.net [80.81.17.52]) (authenticated bits=0) by shymkent.ilbers.de (8.15.2/8.15.2/Debian-8) with ESMTPSA id x1CBHBod014748 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Tue, 12 Feb 2019 12:17:12 +0100 Date: Tue, 12 Feb 2019 12:17:11 +0100 From: Baurzhan Ismagulov To: isar-users Subject: Re: [DISCUSSION] Issues, ToDo and Roadmap Message-ID: <20190212111711.GH805@yssyq.m.ilbers.de> Mail-Followup-To: isar-users References: <71b39226-c243-2fb9-5988-cbf081c7d486@ilbers.de> <00a53485-81f3-1ac8-9649-00f04536f91a@siemens.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <00a53485-81f3-1ac8-9649-00f04536f91a@siemens.com> User-Agent: Mutt/1.10.1 (2018-07-13) X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on shymkent.ilbers.de X-TUID: O9GOvrucQL45 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.