On Thu, Apr 4, 2013 at 6:47 PM, Otavio Salvador <[email protected]> wrote:
> Yes; I think it makes sense but not usually done in Yocto as bisect is > not expected to be fully working in Yocto repositories so I am not > sure about how to handle it. I see pros and cons for both approaches. > What your point of view? In the projects I participate it is not allowed to introduce a commit that builds the breakage, even if it will be fixed in the subsequent commit and I agree that this is a good practice. Or at least your commit could be like: "Since commit xxxxx (gpu-viv-bin-mx6q: Rework package for a single backend use ) the backend suffix from libraries was removed, so remove the LDFLAGS to fix the build" Anyway, I prefer not to break things at the first place. _______________________________________________ meta-freescale mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-freescale
