rauc: split package into 'rauc' for binary and 'rauc-conf' for configuration

[ejoerns]

This allows to build 'rauc' with default TUNE_PKGARCH while ony 'rauc-conf' needs to be build for MACHINE_ARCH as it contains MACHINE-specific configuration.

The rauc target package now RDEPENDS on rauc-conf.

Signed-off-by: Enrico Jorns [email protected]

[ejoerns]

rebased onto master

[mschwan-phytec]

@ejoerns Any news on this PR? Would be nice to see it being merged. :slightly_smiling_face: It would make custom configurations a lot easier to handle.

[ejoerns]

Indeed.

And I currently work myself on a project where this should be quite useful, too. If I find the time, I will test this again in and make it ready for being merged.

[philippderdiedas]

well... how about now? (he asked nicely because does not want to fork it himself)

[ejoerns]

Rebased onto the current master and applied some minor changes.

I was unsure about how strongly I wanted to couple rauc and rauc-conf and decided to add a RRECOMMENDS to a virtual package indirection since I assume that people not only need to want/need to append the rauc-conf recipe but likely provide their own recipes instead. E.g. for differentiating variants on the image level, this is required anyway.

Suggestions or objections welcome.

[jluebbe]

I was unsure about how strongly I wanted to couple rauc and rauc-conf and decided to add a RRECOMMENDS to a virtual package indirection since I assume that people not only need to want/need to append the rauc-conf recipe but likely provide their own recipes instead. E.g. for differentiating variants on the image level, this is required anyway.

With this change, anyone using NO_RECOMMENDATIONS in their image will have no config in their image. If you want to use per-image configs, you can easily drop the RDEPENDS via a bbappend. A comment for that case should be enough.

[ejoerns]

I was unsure about how strongly I wanted to couple rauc and rauc-conf and decided to add a RRECOMMENDS to a virtual package indirection since I assume that people not only need to want/need to append the rauc-conf recipe but likely provide their own recipes instead. E.g. for differentiating variants on the image level, this is required anyway.

With this change, anyone using NO_RECOMMENDATIONS in their image will have no config in their image. If you want to use per-image configs, you can easily drop the RDEPENDS via a bbappend. A comment for that case should be enough.

I wanted to avoid having to bbappend the recipe file for this case and assumed that having no config at all might be noticed.

Note that e.g. systemd pulls in systemd-conf via RRECOMMENDS only, too.

But maybe using RDEPENDS is safer for the transition in the first round, anyway.

[jluebbe]

I wanted to avoid having to bbappend the recipe file for this case and assumed that having no config at all might be noticed.

Note that e.g. systemd pulls in systemd-conf via RRECOMMENDS only, too.

OK. Then it's consistent, and it retract my criticism.

But maybe using RDEPENDS is safer for the transition in the first round, anyway.