On 2018-01-10 16:47, Andreas Reichel wrote: > On Wed, Jan 10, 2018 at 04:11:01PM +0100, Jan Kiszka wrote: >> On 2018-01-10 13:09, [ext] Andreas J. Reichel wrote: >>> From: Andreas Reichel <[email protected]> >>> >>> To really support yocto, we must introduce different branches >>> for used yocto versions. My suggestion is to create the >>> following two branches from master to apply this patch-set to: >>> >>> * rocko >>> * rocko-next >> >> Do Yocto rocko and master already deviate in a relevant degree for us? >> > Yes. There was a question on the mailing list ago about how to build for > rocko. It turned out that there are quite a few things to change: > - stricter dependency tracking (since Pyro) > - different wic module locations > - some requirements to take into account for using autotools/pkgconfig
With master I meant Yocto master. There is no need for a rocko branch yet if Yocto master also works with your patches. We would fork off at the point of introducing a rocko-incompatible patch. Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux -- You received this message because you are subscribed to the Google Groups "EFI Boot Guard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/efibootguard-dev/86607ae3-d7ae-b237-37d0-b49815a2c15b%40siemens.com. For more options, visit https://groups.google.com/d/optout.
