From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by yocto-www.yoctoproject.org (Postfix, from userid 118) id E59ADE00A94; Tue, 11 Aug 2015 03:28:54 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on yocto-www.yoctoproject.org X-Spam-Level: X-Spam-Status: No, score=-6.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_HI autolearn=ham version=3.3.1 X-Spam-HAM-Report: * -5.0 RCVD_IN_DNSWL_HI RBL: Sender listed at http://www.dnswl.org/, high * trust * [192.55.52.88 listed in list.dnswl.org] * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 7C9B3E00A80 for ; Tue, 11 Aug 2015 03:28:52 -0700 (PDT) Received: from orsmga003.jf.intel.com ([10.7.209.27]) by fmsmga101.fm.intel.com with ESMTP; 11 Aug 2015 03:28:51 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.15,652,1432623600"; d="scan'208";a="623268339" Received: from irsmsx103.ger.corp.intel.com ([163.33.3.157]) by orsmga003.jf.intel.com with ESMTP; 11 Aug 2015 03:28:52 -0700 Received: from irsmsx110.ger.corp.intel.com ([169.254.15.29]) by IRSMSX103.ger.corp.intel.com ([169.254.3.149]) with mapi id 14.03.0224.002; Tue, 11 Aug 2015 11:28:48 +0100 From: "Barros Pena, Belen" To: "Reyna, David L (Wind River)" , "toaster@yoctoproject.org" Thread-Topic: Design - Editing package content in custom images Thread-Index: AQHQ0RKU2rngp5de+kC4gkIz0/dS3Z4GegxggAAk0AA= Date: Tue, 11 Aug 2015 10:28:48 +0000 Message-ID: References: <5E53D14CE4667A45B9A06760DE5D13D0825983B1@ALA-MBA.corp.ad.wrs.com> In-Reply-To: <5E53D14CE4667A45B9A06760DE5D13D0825983B1@ALA-MBA.corp.ad.wrs.com> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.5.3.150624 x-originating-ip: [10.237.224.32] MIME-Version: 1.0 Subject: Re: Design - Editing package content in custom images X-BeenThere: toaster@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Web based interface for BitBake List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Aug 2015 10:28:55 -0000 Content-Language: en-US Content-Type: text/plain; charset="iso-8859-1" Content-ID: Content-Transfer-Encoding: quoted-printable On 11/08/2015 09:28, "Reyna, David" wrote: >Hi Bel=E9n, > >The design is great. > >The fundamental gotcha as I mentioned before is that the users will find >that if they go too far deleting packages then (due to the imperfect >nature of the package dependencies) they will eventually end up with an >image that is unbuildable, Well, the image will probably build, although it might not boot. Still, I agree that wouldn't be a great outcome ;) But without creating limitations that do not currently exist in the build system I am not sure how we can avoid this. Instead of having the "all flexible, all powerful" approach of the Yocto Project, we would need to establish a minimum set of packages that all images should have, and make those non-removable. I would not necessarily disagree with this approach for a specific product version of Toaster, but for the Yocto Project generic version it makes me a bit nervous. I wouldn't like to be the one trying to sell the idea to the maintainers ;) >and/or one with the "removed" packages keep magically re-appearing in the >final image. Well, I guess this will happen based on the packages you add. We do have some information about dependencies, and we do show it to users before they add a package. The build history will then give you an accurate picture of what actually happened during a build. Beyond this, I am not sure there is much else we can do. > >I think that we should prepare for that. We should at least have a >disclaimer that package deletion can sometimes lead to unsupported or >surprising states. We should consider/advise some sort of recovery >method, for example. > > * The simplest undo is to delete the broken image and start fresh. This >may be sufficient for this initial release. > * The second simplest is to have a "reset", where you re-start this >image from its baseline source. I quite like this idea of a 'reset' option. It would require knowing what was in the base image. Ed, Michael, Alex: do we know this? What would it take to know? I don't care much if "what was in the image means" 1. the list of packages that were installed by the base image when you created the custom image, or 2. the list of packages installed by the upstream version of the base image (which means there could be some differences between the original package list and the one we can restore) In practice, any of the 2 would be useful. > * The third option is to mark the removed packages in a way that >indicates that they were originally part of the baseline, for example by >having them use a "Re-add package" button label as opposed to "Add >Package". In this manner they have a clue on how to "undo" the changes >visually. Again, this would require remembering what was in the base image somehow, so we need an answer to the question above. From a design perspective, it means 3 types of buttons, which can add a bit of noise. But we could definitely try it and see. > * The forth method is to have an actual "Undo" button, but this would >be a lot of work. We have been talking about adding this. So when it is in place, we should definitely use it in the package addition / removal context. Cheers Bel=E9n > >- David > > >> -----Original Message----- >> From: toaster-bounces@yoctoproject.org [mailto:toaster- >> bounces@yoctoproject.org] On Behalf Of Barros Pena, Belen >> Sent: Friday, August 07, 2015 6:12 AM >> To: toaster@yoctoproject.org >> Subject: [Toaster] Design - Editing package content in custom images >> >> I've documented how we add and remove packages to / from custom images, >> and opened this enhancement >> >> https://bugzilla.yoctoproject.org/show_bug.cgi?id=3D8117 >> >> Design attached to the Bugzilla entry, as usual. The only tricky thing >>is >> the dependency handling, but we used to this in Hob, so I am assuming we >> can do this in Toaster as well. >> >> Any questions / comments, let me know. >> >> Thanks, >> >> Bel=E9n >> >> >> -- >> _______________________________________________ >> toaster mailing list >> toaster@yoctoproject.org >> https://lists.yoctoproject.org/listinfo/toaster