p4: remove broken and 4 years old recipes.
PATCH 1/1 p4: remove broken and 4 years old recipes.
Recipes are broken for all architectures except one (probably arm) because the files in the SRC_URI depend on TARGET_ARCH and the md5/sha256 are presumably valid only for one of these.
Anyone wanting perforce should submit new recipes for new perforce versions.
--- recipes/p4/p4.inc | 72 ------------------------------------------------- recipes/p4/p4_04.2.bb | 18 ------------ recipes/p4/p4_05.2.bb | 18 ------------ 3 files changed, 0 insertions(+), 108 deletions(-) delete mode 100644 recipes/p4/p4.inc delete mode 100644 recipes/p4/p4_04.2.bb delete mode 100644 recipes/p4/p4_05.2.bb
recipes/p4/p4.inc deleted +0 -72
@@ -1,72 +0,0 @@ -# p4 .bb build file -# Copyright (C) 2006, Advanced Micro Devices, Inc. All Rights Reserved -# Released under the MIT license (see /COPYING) - -DESCRIPTION = "Perforce client and server binaries" -HOMEPAGE = "http://www.perforce.com" -LICENSE = "Perforce" - -def p4_arch(d): - import bb, re - arch = bb.data.getVar('TARGET_ARCH', d, 1) - os = bb.data.getVar('TARGET_OS', d, 1) - - if re.match("^linux.*$", os): - r = re.compile("([0-9]+\.[0-9]+).*") - m = r.match(base_read_file(bb.data.expand('${STAGING_KERNEL_DIR}/kernel-abiversion', d))); - os = "linux" - if m and re.match("^.*86.*$", arch): - os = "linux%s" % m.group(1).replace('.','') - - if re.match("^i.86$", arch): - arch = "x86" - elif arch == "x86_64": - arch = "amd64" - elif re.match("^mips.*$", arch): - arch = "mips" - - return "%s%s" % (os, arch) - -P4ARCH = "${@p4_arch(d)}" -P4BASEURL = "http://filehost.perforce.com/perforce/r${PV}/bin.${P4ARCH}" - -#Because these files are all named the same thing, regardless of version or arch -PREMIRRORS="" -DL_DIR="${WORKDIR}/${P4ARCH}" - -SRC_URI="\ - ${P4BASEURL}/p4;name=p4 \ - ${P4BASEURL}/p4api.tar;name=p4api \ - ${P4BASEURL}/p4d;name=p4d \ - ${P4BASEURL}/p4ftpd;name=p4ftpd \ - ${P4BASEURL}/p4p;name=p4p \ - ${P4BASEURL}/p4web;name=p4web" -S = "${WORKDIR}" - -PACKAGES += " ${PN}-server" -FILES_${PN} = " ${bindir}/p4" -FILES_${PN}-server = " ${bindir}/p4d ${bindir}/p4ftpd ${bindir}/p4p ${bindir}/p4web" - -do_stage() { - install -d ${STAGING_INCDIR}/p4api - install -m 0644 *.h ${STAGING_INCDIR}/p4api/ - - oe_libinstall -a libclient ${STAGING_LIBDIR} - oe_libinstall -a librpc ${STAGING_LIBDIR} - oe_libinstall -a libsupp ${STAGING_LIBDIR} -} - -do_install() { - install -d ${D}${bindir} - install -d ${D}${includedir}/p4api - install -d ${D}${libdir} - - install -m 0644 *.h ${D}${includedir}/p4api/ - for p4bin in p4 p4d p4ftpd p4p p4web ; do - install -m 0755 $p4bin ${D}${bindir}/ - done - - oe_libinstall -a libclient ${D}${libdir}/ - oe_libinstall -a librpc ${D}${libdir}/ - oe_libinstall -a libsupp ${D}${libdir}/ -}
recipes/p4/p4_04.2.bb deleted +0 -18
@@ -1,18 +0,0 @@ -# p4 .bb build file -# Copyright (C) 2006, Advanced Micro Devices, Inc. All Rights Reserved -# Released under the MIT license (see /COPYING) - -require p4.inc - -SRC_URI[p4.md5sum] = "ba983759366018ad2d90a7e088f509eb" -SRC_URI[p4.sha256sum] = "de8bce2b3ae085a973dca4f7208c3cb1ab1fdc9bbcc9e3496ad3d56a4923dba0" -SRC_URI[p4api.md5sum] = "1eb1fb53531e09a03f158957016d55a6" -SRC_URI[p4api.sha256sum] = "7d5455c9aa77aea548f3b52f579bf41fff034f0be1c283840b88be401f817792" -SRC_URI[p4d.md5sum] = "690a404af3d916dc7c1cfa5a14a51171" -SRC_URI[p4d.sha256sum] = "e41d44dbc5bd60f2140f0774945154105759b2dabf4c26c097cf754797274e39" -SRC_URI[p4ftpd.md5sum] = "c099df674fb3c249cb1d1984f00d573e" -SRC_URI[p4ftpd.sha256sum] = "9839564335035bc92041fafd93d05a811dc4243bb72269b3afe5ba823f016418" -SRC_URI[p4p.md5sum] = "02de68f26da402689f661662217cd77f" -SRC_URI[p4p.sha256sum] = "24d153529f669ff5fd9dc0d7a09bf7c6e658ee2d2496ab8025a2aaf12425907c" -SRC_URI[p4web.md5sum] = "7bf9967719351c7a0758e20641978358" -SRC_URI[p4web.sha256sum] = "70ebe07343989de042b9ef7866cfca540cfb28458e6c475d516c6916f4feb468"
recipes/p4/p4_05.2.bb deleted +0 -18
@@ -1,18 +0,0 @@ -# p4 .bb build file -# Copyright (C) 2006, Advanced Micro Devices, Inc. All Rights Reserved -# Released under the MIT license (see /COPYING) - -require p4.inc - -SRC_URI[p4.md5sum] = "9bc57695db5885ffac0a352fc17a7f84" -SRC_URI[p4.sha256sum] = "56dd1cb2364b8c8618f9019b641d17d6b307a5a797f3ac31c16a01247554e10c" -SRC_URI[p4api.md5sum] = "7bdb4d9f59a231cc90a8e93709ec1595" -SRC_URI[p4api.sha256sum] = "2e742bf3358f9b8b38f692f4222f96d6901a6faedca155942f58435cee385614" -SRC_URI[p4d.md5sum] = "9a72849bb39cfe19da018271824a3ae1" -SRC_URI[p4d.sha256sum] = "d67bc483b3cbccdcf32db6af21f02d20793a4c3ccc4b758c3a66374b410b73e8" -SRC_URI[p4ftpd.md5sum] = "eb47a4e532fca795893f0c727ae59c84" -SRC_URI[p4ftpd.sha256sum] = "bb5de57d0098e1c6f0d238cc4e658c64579b26fc1df58b9ce59c057fcb5b2f4c" -SRC_URI[p4p.md5sum] = "eed70a3a6af7e59a44d614d4a8022ff0" -SRC_URI[p4p.sha256sum] = "b4b6546d16f161a50337bf9f5dfaf3a4795a3c9b56931e7ee2ace8bcf1863d6e" -SRC_URI[p4web.md5sum] = "e97b15e64be5a3773880f7d66e87a541" -SRC_URI[p4web.sha256sum] = "ce72ef785a92aa8c71b6525e37da49bebab670a046b2ee0c023713f5aa497826"
Signature · 1 line
1.7.1
2010/9/15 Graham Gower <[email protected]>:
Quoted 7 lines
Recipes are broken for all architectures except one (probably arm) because the files in the
SRC_URIdepend onTARGET_ARCHand the md5/sha256 are presumably valid only for one of these.Anyone wanting perforce should submit new recipes for new perforce versions.
Signed-off-by Graham Gower <[email protected]>
Agree with the reasoning of Graham, so:
Actually I am not too keen on having recipes that just "install" an externally downloaded binary blob
(and functionally speaking this does not seem to be something for an embedded system either)
FM
Quoted 9 lines · Frans Meulenbroeks
2010/9/15 Graham Gower<[email protected]>:
Quoted 7 lines
Recipes are broken for all architectures except one (probably arm) because the files in the
SRC_URIdepend onTARGET_ARCHand the md5/sha256 are presumably valid only for one of these.Anyone wanting perforce should submit new recipes for new perforce versions.
Signed-off-by Graham Gower<[email protected]>
Quoted 8 lines
Agree with the reasoning of Graham, so:
Actually I am not too keen on having recipes that just "install" an externally downloaded binary blob
(and functionally speaking this does not seem to be something for an embedded system either)
I will have a need for a recipe to install binary blobs (fpga bin files) into a file system at some point. So this class recipes are needed.
Philip
2010/9/15 Philip Balister <[email protected]>:
Quoted 22 lines · Frans Meulenbroeks
Quoted 12 lines
2010/9/15 Graham Gower<[email protected]>:
Quoted 9 lines
Recipes are broken for all architectures except one (probably arm) because the files in the
SRC_URIdepend onTARGET_ARCHand the md5/sha256 are presumably valid only for one of these.Anyone wanting perforce should submit new recipes for new perforce versions.
Signed-off-by Graham Gower<[email protected]>Quoted 8 lines
Agree with the reasoning of Graham, so:
Actually I am not too keen on having recipes that just "install" an externally downloaded binary blob
(and functionally speaking this does not seem to be something for an embedded system either)
Quoted 4 lines
I will have a need for a recipe to install binary blobs (fpga bin files) into a file system at some point. So this class recipes are needed.
Philip
I'm not saying it should be made technically impossible or so. Actually I do have recipes that install fpga images too, but these live in an overlay.
As I do actual product development with oe I am just not too keen on pulling binary stuff from elsewhere.
And rereading my message I can imagine some misunderstanding.
I wrote
Quoted 2 lines
Quoted 2 lines
(and functionally speaking this does not seem to be something for an embedded system either)
and with this, I wanted to refer to the functionality provided by P4 (a high end SCM if I grasp it right), not to binary recipes in general.
Apologies for the confusion.
Frans
Quoted 17 lines · Philip Balister
Quoted 16 lines · Frans Meulenbroeks
2010/9/15 Graham Gower<[email protected]>:
Quoted 9 lines
Recipes are broken for all architectures except one (probably arm) because the files in the
SRC_URIdepend onTARGET_ARCHand the md5/sha256 are presumably valid only for one of these.Anyone wanting perforce should submit new recipes for new perforce versions.
Signed-off-by Graham Gower<[email protected]>Agree with the reasoning of Graham, so:
Quoted 8 lines
Quoted 4 lines
Actually I am not too keen on having recipes that just "install" an externally downloaded binary blob
(and functionally speaking this does not seem to be something for an embedded system either)I will have a need for a recipe to install binary blobs (fpga bin files) into a file system at some point. So this class recipes are needed.
do you need these m4 recipes ?
Quoted 7 lines
Philip
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Signature · 1 line
-Khem
Quoted 23 lines · Khem Raj
Quoted 22 lines · Philip Balister
Quoted 20 lines · Frans Meulenbroeks
2010/9/15 Graham Gower<[email protected]>:
Quoted 9 lines
Recipes are broken for all architectures except one (probably arm) because the files in the
SRC_URIdepend onTARGET_ARCHand the md5/sha256 are presumably valid only for one of these.Anyone wanting perforce should submit new recipes for new perforce versions.
Signed-off-by Graham Gower<[email protected]>Agree with the reasoning of Graham, so:
Actually I am not too keen on having recipes that just "install" an externally downloaded binary blob
(and functionally speaking this does not seem to be something for an embedded system either)
Quoted 5 lines
Quoted 3 lines
I will have a need for a recipe to install binary blobs (fpga bin files) into a file system at some point. So this class recipes are needed.
do you need these m4 recipes ?
My comments where of a general nature, not about the specific case.
Philip
Quoted 11 lines
Quoted 8 lines
Philip
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel