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

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?