Thanks for the comments. I'm going to clean up the recipes and I'm trying
to upstream some of the
patches to chromium to reduce the maintenance on meta-browser.

Z



On 24 October 2015 at 06:39, Andre McCurdy <[email protected]> wrote:

> On Tue, Oct 13, 2015 at 3:12 AM, Julien Brianceau (jbriance)
> <[email protected]> wrote:
> > Hi,
> >
> >> It still needs some cleanup before upstream, comments are welcome.
> >
> > I think it would be great to take the opportunity to clarify license
> declaration in chromium recipes.
> > Currently, LICENSE is set to BSD only for chromium recipes, through
> chromium.inc file.
> > Archives from http://gsdview.appspot.com/chromium-browser-official
> contain third party source code (ffmpeg for instance) that is not BSD
> licensed, whereas it is compiled by the recipe.
> >
> > Shouldn't licenses from 3rd party code compiled by chromium be declared
> in the recipe as well ?
>
> Yes, they should. The crosswalk browser recipe seems to do a pretty
> good job and could be a starting point for other Chromium based
> recipes.
>
>
> https://github.com/crosswalk-project/meta-crosswalk/blob/master/recipes-crosswalk/crosswalk/crosswalk_12.40.295.0.bb
>
> > Regards,
> >
> > Julien
> > --
> > _______________________________________________
> > Openembedded-devel mailing list
> > [email protected]
> > http://lists.openembedded.org/mailman/listinfo/openembedded-devel
> --
> _______________________________________________
> Openembedded-devel mailing list
> [email protected]
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>



-- 
Zoltan Kuscsik

Senior Software Developer, Linaro Digital Home Group
email: [email protected]
IRC: zoli_ on irc.linaro.org
-- 
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-devel

Reply via email to