Code review comment for lp://staging/~didrocks/ubiquity/minimal-package-list

On 21 February 2018 at 15:42, Sebastien Bacher <email address hidden> wrote:
> Adam, we went with that "alternative" way because we were asked to look at doing something this cycle and we don't currently have the resources in our team to do things the way you consider the proper one.
>
> Didier who looked at that knows the details better but he's on holidays until feature freeze now but from what he said generating on the flight would requiring splitting the seeds and changing more projects to get the diff generated during the iso build and then used in casper. Is that approximatively right? Doing things this way would also make more difficult to remove libreoffice/thunderbird because they would be pulled back by their translations packages (but we could probably workaround that by making the translations depends on the softwares)
>
> Would it be acceptable to keep the current solution if the list is moved to another package that ubiquity? If not would somebody from the installer team be able to help us to get the seed split and the diff generated and made available to the installer?

I believe adam is asking for the "list" to be a file that is dropped
on the .iso by livecd-rootfs, similar to how .disk-info/ is injected,
instead of packaged in the archive as a package. Such that there is no
need to rebuild ubiquity, or any packages in the archive, to update
the list of things to remove, cause a simple iso respin alone will be
enough. (without even rebuilding squashfs).

I don't believe adam is asking for dynamically generating the static
list, but to simply move this static list into ubuntu-cdimage branch
which is code that is used to build desktop-live.iso. No need to
package the static list into a .deb.

--
Regards,

Dimitri.