Hi,

Thanks for your feedback. I apologize for the confusion. I have changed the
recipe to use: LIC_FILES_CHKSUM =
"file://${COMMON_LICENSE_DIR}/BSD;md5=3775480a712fc46a69647678acb234cb"
I have tested this and it works.

I just wanted to confirm that using ${COMMON_LICENSE_DIR} is an acceptable
convention before I apply another patch.


Regards,
Cynthia Chiu

On Wed, Jul 27, 2016 at 6:55 AM, Martin Jansa <[email protected]>
wrote:

> On Wed, Jul 20, 2016 at 11:23:59AM -0600, cynthiachiu wrote:
> > Signed-off-by: cynthiachiu <[email protected]>
> > ---
> >  meta-oe/recipes-extended/canopennode/canopensocket_git.bb | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/meta-oe/recipes-extended/canopennode/canopensocket_git.bb
> b/meta-oe/recipes-extended/canopennode/canopensocket_git.bb
> > index 7c58a26..1e0f7d0 100644
> > --- a/meta-oe/recipes-extended/canopennode/canopensocket_git.bb
> > +++ b/meta-oe/recipes-extended/canopennode/canopensocket_git.bb
> > @@ -1,7 +1,7 @@
> >  SUMMARY = "Linux CANOpen tools"
> >  DESCRIPTION = "Linux CANOpen Protocol Stack Tools"
> >  LICENSE = "GPLv2"
> > -LIC_FILES_CHKSUM =
> "file://gpl-2.0.txt;md5=b234ee4d69f5fce4486a80fdaf4a4263"
> > +LIC_FILES_CHKSUM =
> "file://LICENSE.GPL;md5=b234ee4d69f5fce4486a80fdaf4a4263"
>
> LICENSE.GPL also doesn't exist, FFW test your patches before sending
> them.
>
> Dropped from master-next until someone sends *tested* version.
>
> >  SRC_URI = "gitsm://github.com/CANopenNode/CANopenSocket.git"
> >  SRCREV = "7777653da3a630b0dc02b3fa5ff029d9bc57cd26"
> > --
> > 1.9.1
> >
> > --
> > _______________________________________________
> > Openembedded-devel mailing list
> > [email protected]
> > http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>
> --
> Martin 'JaMa' Jansa     jabber: [email protected]
>
> --
> _______________________________________________
> 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

Reply via email to