En martes, 22 de septiembre de 2020 18:38:45 CEST, Niels Sascha Reedijk
<niels.reedijk@xxxxxxxxx> escribió:
I have identified two gaps in this process. The first is that there will be
issues about new required system packages, that are not yet on the existing
system. Let's say that we decide to break out StyledEdit in a separate package,
but we still want it to be installed by default. I assume the system upgrade
route will not automatically install that package. I assume this is also a gap
in the current online system update. How would we solve this? Would we
introduce the possibility of a FullSync in the solver with a list of required
packages? Or do we solve this at the package level?
Maybe a package with no content but that list of required packages as
dependencies would do. That way you may even have different installation
"profiles": haiku-minimal, haiku-default, haiku-developer, haiku-ponies... that
on update would get new packages as needed. The opposite problem (say
webpositive is retired as a standalone package and included in the haiku one)
would be solved as a package:conflicts or maybe a package:replaces.
That would not require changes to the package manager or a new option. It
wouldn't save current users, though, as they would have to know to install the
new metapackage to enjoy its funcionality.
