Bug 238679

It might be helpful to split up yast2-installation into yast2-installation-stage1 and yast2-installation-stage2.

-stage1 definitely needs yast2-bootloader, grub and lilo, but -stage2 probably does not.

Maybe (don't know for sure) this would even get dependencies to yast2-storage and dependent packages (evms, lvm) out of yast2-installation-stage2.

Yes, that split sounds like a good idea.

Whato do we gain if we split it? We can simply remove the dependency on yast2-bootloader and have the yast2-bootloader in the list of modules which need to be present for 1st stage.
The question is how to deal with the limal-bootloader and perl-Bootloader stuff. It obviously needs to be installed in order to finish 1st stage of the installation properly. It should be enforced during installation, but after installation it should be possible to remove it.

Well, splitting up yast2-installation would fix just this problem. We could make yast2-installation-stage1 require limal-bootloader and perl-bootloader.

Maybe we could limit this to dependencies of the inst-sys: inst-sys requires limal-bootloader and perl-bootloader. This might also be sufficient.

Steffen?

Fine with me, just let me know when you do it. Or adjust BuildRequires
of installation-images yourself.

Splitting installation is indeed good idea, nowadays there are a lot of dependencies that should be solved another way that RPM:requires.

For instance, Installation doesn't need yast2-users and yast2-registration, these steps are only mentioned in the control file but I can imagine system with one user (root) and without registration. We need to solve these dependencies for the control-file itself.

Andreas, what do you think of that? Why don't we install the control-file package which would require or recommend these packages?

Proposal is to leave yast2-installation package and create another yast2-first-stage-installation or yast2-installation-initial and move some YCP clients and modules to that new package (with their dependencies).

Inst-sys would contain:
  * yast2-installation-initial (probing agents, bootloader, storage deps.)
  * yast2-installation (Add-Ons, Workflow logic)

Installed system (second stage) would contain:
  * yast2-installation
  (optionally yast2-installation-initial, of course)

Anyway, I see a big problem when inst-sys practically ignores the dependencies and we have to define what is needed manually. Is there any possibility for automation?

I have no good idea - perhaps you like to discuss this on the yast mailing lists.

OK, problem solved. For the first implementation, yast2-installation will:
  * require only packages that are really needed for the second stage
  * recommend packages that are defined by the workflow
  * ignore required packages for the first stage (fulfilled by inst-sys)

This will solve the problem with dependencies, problem with too many YCP scripts installed in the system can be ignored, 256 kB is nothing.

There is no need to split yast2-installation (thx Jsrain) to more packages, the only quite-needed splitting would be Add-Ons.

Implemented in yast2-installation-2.15.9

Splitting Add-Ons to a separate YaST module might be possible in some next step.

We now have Bug 249679: The first stage really needs yast2-bootloader - in the chroot environment :-(.

So, what shall we do?  Should we revert this?  Or do you have some good ideas?

First stage? that's OK, First stage is covered by the inst-sys, isn't it?
snwint: is yast2-bootloader in inst-sys?

That's the trap we all fail in.  yast2-bootloader is used in first stage but run from the chroot :-(.  Perhaps we might not need everything from the package - but we need it...

Ah, Stano told me that the problem might be because we:
- Switch to the installed system (chroot)
- Write bootloader settings in chroot

Maybe we just need some library, binary, whatever...

Let's close this bug as fixed.
Because many other changes than only "yast2-bootloader" were made.

And let's solve this issue in bug 249679 instead.