Done
Details
Assignee
Igor PecovnikIgor PecovnikFix versions
Reporter
Igor PecovnikIgor PecovnikSprint
NonePriority
Medium
Details
Details
Assignee
Igor Pecovnik
Igor PecovnikFix versions
Reporter
Igor Pecovnik
Igor PecovnikSprint
None
Priority
Created February 28, 2023 at 6:58 PM
Updated March 8, 2023 at 4:34 PM
Resolved March 8, 2023 at 4:34 PM
Packages configs would be nice to clean up as assembly has been completely renewed and perhaps it doesn’t work properly. But it does work somehow. What lists do we need per release:
deboostrap/components (defined once, doesn’t change)
deboostrap/config_desktop/packages (optional, in case we need to force desktop related packages in the debootstrap process)
deboostrap/packages (optional. In some cases we have to declare packages in 1st phase of debootrap. Perhaps today its not needed anymore but needs to be tested)
main/packages (what goes into minimal and server image)
main/packages.additional (what goes into server image)
Those I don’t understand why we need them?
main/config_cli_standard/packages
main/config_cli_standard/packages.additional
(propose merging to main/packages* and removing folders)
The same for desktop.
main/config_desktop/packages (i don’t think we need any of those)
Lets try on Bookworm if any of this is needed. I think we only differentiate between standard and minimal images, nothing else.
Lets try to reduce those lists on minimum as possible in order to gain maintainability.