On 5 May 2017 at 00:48, Max Krummenacher <[email protected]> wrote:
> My concern at the moment is that anything removed now from oe-core will > also be removed > in oe-core pyro in the foreseeable future but the fix or relocation in > meta-xyz will > take time. > Releases only receive critical and security fixes, a recipe will never[1] be removed once a release branch has frozen. > Around the release of morty the same happened with libwnck3 which then > made morty fail for > anyone using libwnck3. > I think you're remembering wrong, or using master. $ git show 5741419426c6f8255d55560e3a4721fa4c68a179 commit 5741419426c6f8255d55560e3a4721fa4c68a179 Author: Alexander Kanavin <[email protected]> Date: Mon Oct 24 15:45:48 2016 +0300 libwnck3: remove the recipe Nothing requires it in oe-core now, so it will be re-added to meta-openembedded. $ git branch -r --contains 5741419426c6f8255d55560e3a4721fa4c68a179 | grep oe-core/ oe-core/master oe-core/pyro It was removed in master *after* morty branched, and was subsequently aded to meta-oe. Ross [1] Almost never. Don't think it's ever happened but we won't remove a recipe from a stable release because we don't like it.
-- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
