Please considering posting these recipe into meta-oe or similar, tomcrypt etc comes up every few months. And posting a recipe to the list implies you want review, right? :)
On 19 October 2016 at 10:12, Markus Volk <f_...@t-online.de> wrote: > DESCRIPTION = "tomcrypt" > HOMEPAGE = " http://www.libtom.net"; <http://www.libtom.net> > LICENSE = "DWTFYW" > Second worst license known to man. :( > LIC_FILES_CHKSUM = "file://${S}/LICENSE;md5=71baacc459522324ef3e2b9e052e81 > 80" > These URLs are relative to ${S} so just file://LICENSE works. > SRC_URI = "git://github.com/libtom/libtomcrypt.git;branch=develop \ > " > > SRCREV = "${AUTOREV}" > In general it's recommended to use a fixed SHA and then override SRVREV if you need to for testing/CI/whatever. > PV = "${SRCPV}" > PR = "1" > No need for PR in general. > S = "${WORKDIR}/git" > > inherit autotools-brokensep > Boo. Is upstream fixable or is it beyond help? > SRC_URI[md5sum] = "d2f152e4dc83ee4cdb1b4f1a4866fe7f" > SRC_URI[sha256sum] = "d0ff89397f9a5fd1d13b1cbc419d5d > 426e14473135515d72bfcb58e5babf5032" > > No need for SRC_URI if you're using git fetcher. Ross
-- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
