Hi Brian, Thanks for looking at those dialogs. It really helps. A couple of questions / commments inline.
On 18/01/2016 20:54, "Brian Avery" <[email protected]> wrote: >I would like to do number 1. We could add it as a bug for 2.1; we >have enough information to enable it. Following the list by hand and >then realizing I forgot to remove one of them and therefore >alsa-server gets installed anyway is an irritation I don't think we >should inflict. > >number 2 is quite a bit harder. For number 2 it is more likely what >we walk the list and show at the top level which packages no longer >have dependencies. The way you present it number 2 makes sense if >glibc were installed/required only by alsa-conf-base but generally >they are pulled in by more than one package That's the thing: they would only show up in that dialog when they are pulled in only by the package you are removing. If any other package is bringing them in, they woudn't show up. >and keeping track of that is not helpful. >However, just showing that the following packages were >brought in as a dependency and nothing requires them anymore should be >doable. Right, if I understand correctly, you are suggesting we use the package list to present this kind of "orphan" packages. Is that the case? > >Linux does something like this: >" >The following package was automatically installed and is no longer >required: > > libmpdec2 >" We could provide a similar message, I guess, in the reverse dependencies column when applicable. Would that work? Cheers, Belén > >-b > >On Thu, Jan 7, 2016 at 5:39 AM, Barros Pena, Belen ><[email protected]> wrote: >> While discussing some of our issues with image customisation in >>Toaster, I >> realised the designs for removing packages with dependencies are >> incomplete. >> >> Removing a package can result in 2 different situations: >> >> 1. The package you are removing is required by other packages in your >>image >> >> 2. The package you are removing generates orphan packages (packages that >> are no longer required since they were only added to satisfy the >> dependencies of the package you are removing) >> >> Ideally, Toaster would handle both situations. In both cases, we would >> show a message to the user with some options. >> >> For 1, the message would show you the list of packages that are required >> by the package you are removing, and would give you the option to remove >> them all, or cancel the removal (see attached 1.png). >> >> For 2, the message would show you the list of orphan dependencies, and >> give you the option to choose which ones you'd like to remove and which >> ones you'd like to keep (see attached 2.png). >> >> I understand if we cannot do number 2 in version 1 of image >>customisation, >> but what about number 1? Any comments / feedback on the dialogs? Am I >> missing any other cases that can come up when removing packages? >> >> Thanks! >> >> Belén >> >> >> >> -- >> _______________________________________________ >> toaster mailing list >> [email protected] >> https://lists.yoctoproject.org/listinfo/toaster >> -- _______________________________________________ toaster mailing list [email protected] https://lists.yoctoproject.org/listinfo/toaster
