On 19 September 2017 at 00:16, Trevor Woerner <twoer...@gmail.com> wrote:
> It doesn't make sense to carry these large patches against pseudo in > OE itself. Isn't pseudo one of the tools under The Yocto Project > umbrella? Adding patches to a recipe is what happens when upstream > isn't under our control, isn't responsive, or isn't cooperating. > > Can someone volunteer to be the active maintainer of it and get commit > access? I'll volunteer, if nobody else does. But if I become the > maintainer, I'll need some time to get up-to-speed, or some potential > support from the current maintainer. This patch may not yet be acceptable "upstream" but is sufficient for our purposes, and we've obviously got a good relationship with "upstream" so carrying it in oe-core is a short-term measure. Ross
-- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
