How Factory or ALP Workbench select bootstrap packages?
Hello, May I ask how do you select packages for "SUSE:ALP:Workbench:1.0", to make it can be built everything else from itself? Is there scripts to do so? I notice some revision's comment like "initial import", "initial import needed for building eigen3:docs,eigen3", etc. How do you solve dependency problem? Manually? Another similar question: May I ask how do you select bootstrap package for "Rings:0-Bootstrap", "Rings:1-MinimalX"? Thank you.
Le lundi 29 janvier 2024 à 09:49 +0000, Obs Geeko via openSUSE Factory a écrit :
Hello,
May I ask how do you select packages for "SUSE:ALP:Workbench:1.0", to make it can be built everything else from itself? Is there scripts to do so?
Workbench packagelist list was done manually, by gradually importing packages until we had a almost complete set of packages being able to bootstrap. -- Frederic CROZAT Enterprise Linux OS and Containers Architect SUSE
Hello Frederic, Thanks for your reply. May I ask "Rings:0-Bootstrap", "Rings:1-MinimalX" are also selected manually? It looks like only using "Rings:0-Bootstrap" packages without "Factory" cannot build all "Rings:1-MinimalX". It still needs extra dependencies from "Factory". Do we do this intentionally? Thanks again. Best regards. Frederic Crozat wrote:
Hello, May I ask how do you select packages for "SUSE:ALP:Workbench:1.0", to make it can be built everything else from itself? Is there scripts to do so? Workbench packagelist list was done manually, by gradually importing
Le lundi 29 janvier 2024 à 09:49 +0000, Obs Geeko via openSUSE Factory a écrit : packages until we had a almost complete set of packages being able to bootstrap.
On Tue, 2024-01-30 at 13:06 +0000, Obs Geeko via openSUSE Factory wrote:
Hello Frederic,
Thanks for your reply. May I ask "Rings:0-Bootstrap", "Rings:1-MinimalX" are also selected manually?
The rings are indeed manually curated, the grow and shrink on needs (growing is easy: whenever something misses deps, it is being added, for shrinking we have scripts to give hints what might go out)
It looks like only using "Rings:0-Bootstrap" packages without "Factory" cannot build all "Rings:1-MinimalX". It still needs extra dependencies from "Factory". Do we do this intentionally? Thanks again.
Ring0 is a bit special: it builds on its own, except build, rpmlint- mini, rpmlint:strict and kernel-obs-build are being copied from Ring1 down to Ring0 Build deps for those support packages are too extensive) The aggregated binaries are defined in https://build.opensuse.org/package/view_file/openSUSE:Factory:Rings:0-Bootst... Ring1 then builds against Ring0. In order to get Ring1 going, things like the rust and java compilers need to have binaries injected (usually a one-off copy from Factory) Hth, Dominique
May I ask "Rings:0-Bootstrap", "Rings:1-MinimalX" are also selected manually? The rings are indeed manually curated, the grow and shrink on needs (growing is easy: whenever something misses deps, it is being added, for shrinking we have scripts to give hints what might go out)
May I ask where can we find the scripts for shrinking the deps/packages in one project? Thank you.
participants (3)
-
Dominique Leuenberger -
Frederic Crozat -
Obs Geeko