Re: [Buildroot] [PATCH v3 2/3] package/dracut: new host package

[Thierry Bultel <thierry.bultel@linatsea.fr>]

> And what about glibc? musl?
>
> Can we unconditionally install the modules and change their check()
> functions to decide whther the moduels is usable or not? Or something
> else dynamic?

There is not extra work to do for glibc (this is my default 
configuration). I did not test with musl, yet.

>> +ifeq ($(BR2_INIT_BUSYBOX),y)
>> +define HOST_DRACUT_POST_INSTALL_BUSYBOX_MODULE
>> +	$(INSTALL) -D -m 0755 package/dracut/05busybox-buildroot/module-setup.sh \
>> +		$(HOST_DIR)/lib/dracut/modules.d/05busybox-buildroot/module-setup.sh
>> +endef
>> +HOST_DRACUT_POST_INSTALL_HOOKS+=HOST_DRACUT_POST_INSTALL_BUSYBOX_MODULE
> And what about systemd as an init system? openrc? sysv-init? Others?
Keeping in mind that systemd is the officially supported init system by 
dracut, there is no extra work
for it. However, I brought support for busybox init, through the above 
dracut module (05busybox-buildroot).
Adding support for the other ones could be done later, so I suggest we 
simply disable dracut when the
init system is not supported; by adding

     depends on !BR2_INIT_SYSV
     depends on !BR2_INIT_OPENRC

in Config.in.host; with the appropriate comment. Does that sound 
acceptable ?

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot