Generally things acceptable to oe-core must be a) broadly useful to many people b) regularly tested on the autobuilder. I don't think AUTOREV recipes would fulfil either. Besides, if gstreamer is ok for AUTOREV, then why not other components?
But you can easily have such AUTOREV recipes in a separate layer. In fact, right here: https://github.com/OSSystems/meta-gstreamer1.0/tree/master/recipes-multimedia/gstreamer Meson conversion is very welcome, right now is the best time (as later on there will be a feature freeze). You don't have to convert them all at once. Alex On Mon, 3 Jun 2019 at 15:47, Philippe Normand <[email protected]> wrote: > Hi folks, > > It would be convenient to have _git.bb GStreamer recipes, for > development purposes. There were some in the past but they were not > very well maintained and they had outdated SRCREVs. Would it be > acceptable to include _git.bb recipes relying on ${AUTOREV} in the > tree? > > We also plan to migrate the recipes to Meson, especially because the > autotools build will be removed from GStreamer upstream, most probably > before the 1.18 stable release. > > Philippe > > -- > _______________________________________________ > Openembedded-core mailing list > [email protected] > http://lists.openembedded.org/mailman/listinfo/openembedded-core >
-- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
