* [PATCH] add recipe cim-schema, cim-schema-docs and license file DMTF.
@ 2014-06-12 3:26 Yao Xinpan
2014-06-12 8:56 ` Martin Jansa
0 siblings, 1 reply; 6+ messages in thread
From: Yao Xinpan @ 2014-06-12 3:26 UTC (permalink / raw)
To: yocto
Signed-off-by: Yao Xinpan <yaoxp@cn.fujitsu.com>
---
meta/files/common-licenses/DMTF | 34 ++++++++++++++++++++++
.../cim-schema/cim-schema-docs_2.40.0.bb | 23 +++++++++++++++
meta/recipes-support/cim-schema/cim-schema.inc | 9 ++++++
.../cim-schema/cim-schema_2.40.0.bb | 31 ++++++++++++++++++++
meta/recipes-support/cim-schema/files/LICENSE | 34 ++++++++++++++++++++++
5 files changed, 131 insertions(+)
create mode 100644 meta/files/common-licenses/DMTF
create mode 100644 meta/recipes-support/cim-schema/cim-schema-docs_2.40.0.bb
create mode 100644 meta/recipes-support/cim-schema/cim-schema.inc
create mode 100644 meta/recipes-support/cim-schema/cim-schema_2.40.0.bb
create mode 100644 meta/recipes-support/cim-schema/files/LICENSE
diff --git a/meta/files/common-licenses/DMTF b/meta/files/common-licenses/DMTF
new file mode 100644
index 0000000..54a2812
--- /dev/null
+++ b/meta/files/common-licenses/DMTF
@@ -0,0 +1,34 @@
+// Copyright 1998-2008 Distributed Management Task Force, Inc. (DMTF).
+// All rights reserved.
+// DMTF is a not-for-profit association of industry members dedicated
+// to promoting enterprise and systems management and interoperability.
+// DMTF specifications and documents may be reproduced by
+// members and non-members, provided that correct attribution is given.
+// As DMTF specifications may be revised from time to time,
+// the particular version and release date should always be noted.
+//
+// Implementation of certain elements of this standard or proposed
+// standard may be subject to third party patent rights, including
+// provisional patent rights (herein "patent rights"). DMTF makes
+// no representations to users of the standard as to the existence
+// of such rights, and is not responsible to recognize, disclose, or
+// identify any or all such third party patent right, owners or
+// claimants, nor for any incomplete or inaccurate identification or
+// disclosure of such rights, owners or claimants. DMTF shall have no
+// liability to any party, in any manner or circumstance, under any
+// legal theory whatsoever, for failure to recognize, disclose, or
+// identify any such third party patent rights, or for such party's
+// reliance on the standard or incorporation thereof in its product,
+// protocols or testing procedures. DMTF shall have no liability to
+// any party implementing such standard, whether such implementation
+// is foreseeable or not, nor to any patent owner or claimant, and shall
+// have no liability or responsibility for costs or losses incurred if
+// a standard is withdrawn or modified after publication, and shall be
+// indemnified and held harmless by any party implementing the
+// standard from any and all claims of infringement by a patent owner
+// for such implementations.
+//
+// For information about patents held by third-parties which have
+// notified the DMTF that, in their opinion, such patent may relate to
+// or impact implementations of DMTF standards, visit
+// http://www.dmtf.org/about/policies/disclosures.php.
diff --git a/meta/recipes-support/cim-schema/cim-schema-docs_2.40.0.bb b/meta/recipes-support/cim-schema/cim-schema-docs_2.40.0.bb
new file mode 100644
index 0000000..06c0dd9
--- /dev/null
+++ b/meta/recipes-support/cim-schema/cim-schema-docs_2.40.0.bb
@@ -0,0 +1,23 @@
+require cim-schema.inc
+
+LICENSE = "DMTF"
+
+SRC_URI = "http://dmtf.org/sites/default/files/cim/cim_schema_v2400/cim_schema_${PV}Final-Doc.zip \
+ file://LICENSE \
+ "
+SRC_URI[md5sum] = "3d01940bc1085c6c42184c25fb61f739"
+SRC_URI[sha256sum] = "3174cf0f8657b19d80dc59e184778d8e553da424728cb2966fe9d5428dd84267"
+LIC_FILES_CHKSUM = "file://${WORKDIR}/LICENSE;md5=eecc6f71a56ff3caf17f15bf7aeac7b4"
+
+do_unpack() {
+ unzip -q ${DL_DIR}/cim_schema_${PV}Final-Doc.zip -d ${S}
+ cp -f ${FILE_DIRNAME}/files/LICENSE ${WORKDIR}/
+}
+
+do_install() {
+ install -d -m 0755 ${D}${datadir}/doc/cim-schema-${PV}-docs
+ cp -a ${S}/* ${D}${datadir}/doc/cim-schema-${PV}-docs
+}
+
+FILES_${PN} = "${datadir}/doc/*"
+FILES_${PN}-doc = ""
diff --git a/meta/recipes-support/cim-schema/cim-schema.inc b/meta/recipes-support/cim-schema/cim-schema.inc
new file mode 100644
index 0000000..e35bff6
--- /dev/null
+++ b/meta/recipes-support/cim-schema/cim-schema.inc
@@ -0,0 +1,9 @@
+SUMMARY = "Common Information Model (CIM) Schema"
+DESCRIPTION = "Common Information Model (CIM) is a model for describing overall\
+management information in a network or enterprise environment. CIM\
+consists of a specification and a schema. The specification defines the\
+details for integration with other management models. The schema\
+provides the actual model descriptions."
+
+HOMEPAGE = "http://www.dmtf.org/"
+SECTION = "Development/Libraries"
diff --git a/meta/recipes-support/cim-schema/cim-schema_2.40.0.bb b/meta/recipes-support/cim-schema/cim-schema_2.40.0.bb
new file mode 100644
index 0000000..ff6c29d
--- /dev/null
+++ b/meta/recipes-support/cim-schema/cim-schema_2.40.0.bb
@@ -0,0 +1,31 @@
+require cim-schema.inc
+
+LICENSE = "DMTF"
+
+SRC_URI = "http://dmtf.org/sites/default/files/cim/cim_schema_v2400/cim_schema_${PV}Final-MOFs.zip \
+ file://LICENSE \
+ "
+SRC_URI[md5sum] = "a9bdf17c7374e3b5b7adeaac4842c4ad"
+SRC_URI[sha256sum] = "dbfa3064ea427acd71a4bebbc172ca2dc44b0b09a6d83b0945b9ffa988a9058a"
+LIC_FILES_CHKSUM = "file://${WORKDIR}/LICENSE;md5=eecc6f71a56ff3caf17f15bf7aeac7b4"
+
+do_unpack() {
+ unzip -q ${DL_DIR}/cim_schema_${PV}Final-MOFs.zip -d ${S}
+ cp -f ${FILE_DIRNAME}/files/LICENSE ${WORKDIR}/
+}
+
+do_install() {
+ install -d -m 0755 ${D}${datadir}/mof/cimv${PV}/
+ install -d -m 0755 ${D}${datadir}/doc/cim-schema-${PV}
+ install -m 644 ${WORKDIR}/LICENSE ${D}${datadir}/doc/cim-schema-${PV}
+
+ cp -a ${S}/* ${D}${datadir}/mof/cimv${PV}/
+ for i in `find ${D}${datadir}/mof/cimv${PV} -name "*.mof"`; do
+ sed -i -e 's/\r//g' $i
+ done
+ ln -s cimv${PV} ${D}${datadir}/mof/cim-current
+ ln -s cim_schema_${PV}.mof ${D}${datadir}/mof/cim-current/CIM_Schema.mof
+}
+
+FILES_${PN} = "${datadir}/mof/* ${datadir}/doc/*"
+FILES_${PN}-doc = ""
diff --git a/meta/recipes-support/cim-schema/files/LICENSE b/meta/recipes-support/cim-schema/files/LICENSE
new file mode 100644
index 0000000..54a2812
--- /dev/null
+++ b/meta/recipes-support/cim-schema/files/LICENSE
@@ -0,0 +1,34 @@
+// Copyright 1998-2008 Distributed Management Task Force, Inc. (DMTF).
+// All rights reserved.
+// DMTF is a not-for-profit association of industry members dedicated
+// to promoting enterprise and systems management and interoperability.
+// DMTF specifications and documents may be reproduced by
+// members and non-members, provided that correct attribution is given.
+// As DMTF specifications may be revised from time to time,
+// the particular version and release date should always be noted.
+//
+// Implementation of certain elements of this standard or proposed
+// standard may be subject to third party patent rights, including
+// provisional patent rights (herein "patent rights"). DMTF makes
+// no representations to users of the standard as to the existence
+// of such rights, and is not responsible to recognize, disclose, or
+// identify any or all such third party patent right, owners or
+// claimants, nor for any incomplete or inaccurate identification or
+// disclosure of such rights, owners or claimants. DMTF shall have no
+// liability to any party, in any manner or circumstance, under any
+// legal theory whatsoever, for failure to recognize, disclose, or
+// identify any such third party patent rights, or for such party's
+// reliance on the standard or incorporation thereof in its product,
+// protocols or testing procedures. DMTF shall have no liability to
+// any party implementing such standard, whether such implementation
+// is foreseeable or not, nor to any patent owner or claimant, and shall
+// have no liability or responsibility for costs or losses incurred if
+// a standard is withdrawn or modified after publication, and shall be
+// indemnified and held harmless by any party implementing the
+// standard from any and all claims of infringement by a patent owner
+// for such implementations.
+//
+// For information about patents held by third-parties which have
+// notified the DMTF that, in their opinion, such patent may relate to
+// or impact implementations of DMTF standards, visit
+// http://www.dmtf.org/about/policies/disclosures.php.
--
1.8.4.2
^ permalink raw reply related [flat|nested] 6+ messages in thread
* Re: [PATCH] add recipe cim-schema, cim-schema-docs and license file DMTF.
2014-06-12 3:26 [PATCH] add recipe cim-schema, cim-schema-docs and license file DMTF Yao Xinpan
@ 2014-06-12 8:56 ` Martin Jansa
2014-06-12 9:27 ` Burton, Ross
0 siblings, 1 reply; 6+ messages in thread
From: Martin Jansa @ 2014-06-12 8:56 UTC (permalink / raw)
To: Yao Xinpan; +Cc: yocto
[-- Attachment #1: Type: text/plain, Size: 9578 bytes --]
On Thu, Jun 12, 2014 at 11:26:57AM +0800, Yao Xinpan wrote:
> Signed-off-by: Yao Xinpan <yaoxp@cn.fujitsu.com>
Why is this recipe needed in oe-core layer? Wouldn't meta-networking be
more suitable?
The patch also belongs to oe-core ML not yocto.
> ---
> meta/files/common-licenses/DMTF | 34 ++++++++++++++++++++++
> .../cim-schema/cim-schema-docs_2.40.0.bb | 23 +++++++++++++++
> meta/recipes-support/cim-schema/cim-schema.inc | 9 ++++++
> .../cim-schema/cim-schema_2.40.0.bb | 31 ++++++++++++++++++++
> meta/recipes-support/cim-schema/files/LICENSE | 34 ++++++++++++++++++++++
> 5 files changed, 131 insertions(+)
> create mode 100644 meta/files/common-licenses/DMTF
> create mode 100644 meta/recipes-support/cim-schema/cim-schema-docs_2.40.0.bb
> create mode 100644 meta/recipes-support/cim-schema/cim-schema.inc
> create mode 100644 meta/recipes-support/cim-schema/cim-schema_2.40.0.bb
> create mode 100644 meta/recipes-support/cim-schema/files/LICENSE
>
> diff --git a/meta/files/common-licenses/DMTF b/meta/files/common-licenses/DMTF
> new file mode 100644
> index 0000000..54a2812
> --- /dev/null
> +++ b/meta/files/common-licenses/DMTF
> @@ -0,0 +1,34 @@
> +// Copyright 1998-2008 Distributed Management Task Force, Inc. (DMTF).
> +// All rights reserved.
> +// DMTF is a not-for-profit association of industry members dedicated
> +// to promoting enterprise and systems management and interoperability.
> +// DMTF specifications and documents may be reproduced by
> +// members and non-members, provided that correct attribution is given.
> +// As DMTF specifications may be revised from time to time,
> +// the particular version and release date should always be noted.
> +//
> +// Implementation of certain elements of this standard or proposed
> +// standard may be subject to third party patent rights, including
> +// provisional patent rights (herein "patent rights"). DMTF makes
> +// no representations to users of the standard as to the existence
> +// of such rights, and is not responsible to recognize, disclose, or
> +// identify any or all such third party patent right, owners or
> +// claimants, nor for any incomplete or inaccurate identification or
> +// disclosure of such rights, owners or claimants. DMTF shall have no
> +// liability to any party, in any manner or circumstance, under any
> +// legal theory whatsoever, for failure to recognize, disclose, or
> +// identify any such third party patent rights, or for such party's
> +// reliance on the standard or incorporation thereof in its product,
> +// protocols or testing procedures. DMTF shall have no liability to
> +// any party implementing such standard, whether such implementation
> +// is foreseeable or not, nor to any patent owner or claimant, and shall
> +// have no liability or responsibility for costs or losses incurred if
> +// a standard is withdrawn or modified after publication, and shall be
> +// indemnified and held harmless by any party implementing the
> +// standard from any and all claims of infringement by a patent owner
> +// for such implementations.
> +//
> +// For information about patents held by third-parties which have
> +// notified the DMTF that, in their opinion, such patent may relate to
> +// or impact implementations of DMTF standards, visit
> +// http://www.dmtf.org/about/policies/disclosures.php.
> diff --git a/meta/recipes-support/cim-schema/cim-schema-docs_2.40.0.bb b/meta/recipes-support/cim-schema/cim-schema-docs_2.40.0.bb
> new file mode 100644
> index 0000000..06c0dd9
> --- /dev/null
> +++ b/meta/recipes-support/cim-schema/cim-schema-docs_2.40.0.bb
> @@ -0,0 +1,23 @@
> +require cim-schema.inc
> +
> +LICENSE = "DMTF"
> +
> +SRC_URI = "http://dmtf.org/sites/default/files/cim/cim_schema_v2400/cim_schema_${PV}Final-Doc.zip \
> + file://LICENSE \
> + "
> +SRC_URI[md5sum] = "3d01940bc1085c6c42184c25fb61f739"
> +SRC_URI[sha256sum] = "3174cf0f8657b19d80dc59e184778d8e553da424728cb2966fe9d5428dd84267"
> +LIC_FILES_CHKSUM = "file://${WORKDIR}/LICENSE;md5=eecc6f71a56ff3caf17f15bf7aeac7b4"
> +
> +do_unpack() {
> + unzip -q ${DL_DIR}/cim_schema_${PV}Final-Doc.zip -d ${S}
> + cp -f ${FILE_DIRNAME}/files/LICENSE ${WORKDIR}/
> +}
> +
> +do_install() {
> + install -d -m 0755 ${D}${datadir}/doc/cim-schema-${PV}-docs
> + cp -a ${S}/* ${D}${datadir}/doc/cim-schema-${PV}-docs
> +}
> +
> +FILES_${PN} = "${datadir}/doc/*"
> +FILES_${PN}-doc = ""
> diff --git a/meta/recipes-support/cim-schema/cim-schema.inc b/meta/recipes-support/cim-schema/cim-schema.inc
> new file mode 100644
> index 0000000..e35bff6
> --- /dev/null
> +++ b/meta/recipes-support/cim-schema/cim-schema.inc
> @@ -0,0 +1,9 @@
> +SUMMARY = "Common Information Model (CIM) Schema"
> +DESCRIPTION = "Common Information Model (CIM) is a model for describing overall\
> +management information in a network or enterprise environment. CIM\
> +consists of a specification and a schema. The specification defines the\
> +details for integration with other management models. The schema\
> +provides the actual model descriptions."
> +
> +HOMEPAGE = "http://www.dmtf.org/"
> +SECTION = "Development/Libraries"
> diff --git a/meta/recipes-support/cim-schema/cim-schema_2.40.0.bb b/meta/recipes-support/cim-schema/cim-schema_2.40.0.bb
> new file mode 100644
> index 0000000..ff6c29d
> --- /dev/null
> +++ b/meta/recipes-support/cim-schema/cim-schema_2.40.0.bb
> @@ -0,0 +1,31 @@
> +require cim-schema.inc
> +
> +LICENSE = "DMTF"
> +
> +SRC_URI = "http://dmtf.org/sites/default/files/cim/cim_schema_v2400/cim_schema_${PV}Final-MOFs.zip \
> + file://LICENSE \
> + "
> +SRC_URI[md5sum] = "a9bdf17c7374e3b5b7adeaac4842c4ad"
> +SRC_URI[sha256sum] = "dbfa3064ea427acd71a4bebbc172ca2dc44b0b09a6d83b0945b9ffa988a9058a"
> +LIC_FILES_CHKSUM = "file://${WORKDIR}/LICENSE;md5=eecc6f71a56ff3caf17f15bf7aeac7b4"
> +
> +do_unpack() {
> + unzip -q ${DL_DIR}/cim_schema_${PV}Final-MOFs.zip -d ${S}
> + cp -f ${FILE_DIRNAME}/files/LICENSE ${WORKDIR}/
> +}
> +
> +do_install() {
> + install -d -m 0755 ${D}${datadir}/mof/cimv${PV}/
> + install -d -m 0755 ${D}${datadir}/doc/cim-schema-${PV}
> + install -m 644 ${WORKDIR}/LICENSE ${D}${datadir}/doc/cim-schema-${PV}
> +
> + cp -a ${S}/* ${D}${datadir}/mof/cimv${PV}/
> + for i in `find ${D}${datadir}/mof/cimv${PV} -name "*.mof"`; do
> + sed -i -e 's/\r//g' $i
> + done
> + ln -s cimv${PV} ${D}${datadir}/mof/cim-current
> + ln -s cim_schema_${PV}.mof ${D}${datadir}/mof/cim-current/CIM_Schema.mof
> +}
> +
> +FILES_${PN} = "${datadir}/mof/* ${datadir}/doc/*"
> +FILES_${PN}-doc = ""
> diff --git a/meta/recipes-support/cim-schema/files/LICENSE b/meta/recipes-support/cim-schema/files/LICENSE
> new file mode 100644
> index 0000000..54a2812
> --- /dev/null
> +++ b/meta/recipes-support/cim-schema/files/LICENSE
> @@ -0,0 +1,34 @@
> +// Copyright 1998-2008 Distributed Management Task Force, Inc. (DMTF).
> +// All rights reserved.
> +// DMTF is a not-for-profit association of industry members dedicated
> +// to promoting enterprise and systems management and interoperability.
> +// DMTF specifications and documents may be reproduced by
> +// members and non-members, provided that correct attribution is given.
> +// As DMTF specifications may be revised from time to time,
> +// the particular version and release date should always be noted.
> +//
> +// Implementation of certain elements of this standard or proposed
> +// standard may be subject to third party patent rights, including
> +// provisional patent rights (herein "patent rights"). DMTF makes
> +// no representations to users of the standard as to the existence
> +// of such rights, and is not responsible to recognize, disclose, or
> +// identify any or all such third party patent right, owners or
> +// claimants, nor for any incomplete or inaccurate identification or
> +// disclosure of such rights, owners or claimants. DMTF shall have no
> +// liability to any party, in any manner or circumstance, under any
> +// legal theory whatsoever, for failure to recognize, disclose, or
> +// identify any such third party patent rights, or for such party's
> +// reliance on the standard or incorporation thereof in its product,
> +// protocols or testing procedures. DMTF shall have no liability to
> +// any party implementing such standard, whether such implementation
> +// is foreseeable or not, nor to any patent owner or claimant, and shall
> +// have no liability or responsibility for costs or losses incurred if
> +// a standard is withdrawn or modified after publication, and shall be
> +// indemnified and held harmless by any party implementing the
> +// standard from any and all claims of infringement by a patent owner
> +// for such implementations.
> +//
> +// For information about patents held by third-parties which have
> +// notified the DMTF that, in their opinion, such patent may relate to
> +// or impact implementations of DMTF standards, visit
> +// http://www.dmtf.org/about/policies/disclosures.php.
> --
> 1.8.4.2
>
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH] add recipe cim-schema, cim-schema-docs and license file DMTF.
2014-06-12 8:56 ` Martin Jansa
@ 2014-06-12 9:27 ` Burton, Ross
2014-06-18 7:30 ` yaoxp
0 siblings, 1 reply; 6+ messages in thread
From: Burton, Ross @ 2014-06-12 9:27 UTC (permalink / raw)
To: Yao Xinpan; +Cc: yocto@yoctoproject.org
On 12 June 2014 09:56, Martin Jansa <martin.jansa@gmail.com> wrote:
> Why is this recipe needed in oe-core layer? Wouldn't meta-networking be
> more suitable?
>
> The patch also belongs to oe-core ML not yocto.
Agreed, unless there's a strong reason then this should go to
meta-networking (so send to the openembedded-devel list).
Ross
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH] add recipe cim-schema, cim-schema-docs and license file DMTF.
2014-06-12 9:27 ` Burton, Ross
@ 2014-06-18 7:30 ` yaoxp
2014-06-18 7:54 ` Martin Jansa
0 siblings, 1 reply; 6+ messages in thread
From: yaoxp @ 2014-06-18 7:30 UTC (permalink / raw)
To: Burton, Ross; +Cc: yocto@yoctoproject.org
Why not in oe-core?
What recipe can be put in oe-core, and what recipe can be put in meta-oe?
thanks
Yao Xinpan
> -----Original Message-----
> From: Burton, Ross [mailto:ross.burton@intel.com]
> Sent: Thursday, June 12, 2014 5:27 PM
> To: Yao, Xinpan
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] [PATCH] add recipe cim-schema, cim-schema-docs and
> license file DMTF.
>
> On 12 June 2014 09:56, Martin Jansa <martin.jansa@gmail.com> wrote:
> > Why is this recipe needed in oe-core layer? Wouldn't meta-networking
> > be more suitable?
> >
> > The patch also belongs to oe-core ML not yocto.
>
> Agreed, unless there's a strong reason then this should go to meta-networking
> (so send to the openembedded-devel list).
>
> Ross
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH] add recipe cim-schema, cim-schema-docs and license file DMTF.
2014-06-18 7:30 ` yaoxp
@ 2014-06-18 7:54 ` Martin Jansa
2014-06-20 6:24 ` yaoxp
0 siblings, 1 reply; 6+ messages in thread
From: Martin Jansa @ 2014-06-18 7:54 UTC (permalink / raw)
To: yaoxp@cn.fujitsu.com; +Cc: yocto@yoctoproject.org
[-- Attachment #1: Type: text/plain, Size: 1273 bytes --]
On Wed, Jun 18, 2014 at 07:30:49AM +0000, yaoxp@cn.fujitsu.com wrote:
> Why not in oe-core?
> What recipe can be put in oe-core, and what recipe can be put in meta-oe?
"core" recipes which are used by most if not all OE builds
"opt-in" extra recipes go to different "topic" layers
nobody needed or asked for cim until now, so it's not "core" by this
definition.
> > -----Original Message-----
> > From: Burton, Ross [mailto:ross.burton@intel.com]
> > Sent: Thursday, June 12, 2014 5:27 PM
> > To: Yao, Xinpan
> > Cc: yocto@yoctoproject.org
> > Subject: Re: [yocto] [PATCH] add recipe cim-schema, cim-schema-docs and
> > license file DMTF.
> >
> > On 12 June 2014 09:56, Martin Jansa <martin.jansa@gmail.com> wrote:
> > > Why is this recipe needed in oe-core layer? Wouldn't meta-networking
> > > be more suitable?
> > >
> > > The patch also belongs to oe-core ML not yocto.
> >
> > Agreed, unless there's a strong reason then this should go to meta-networking
> > (so send to the openembedded-devel list).
> >
> > Ross
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH] add recipe cim-schema, cim-schema-docs and license file DMTF.
2014-06-18 7:54 ` Martin Jansa
@ 2014-06-20 6:24 ` yaoxp
0 siblings, 0 replies; 6+ messages in thread
From: yaoxp @ 2014-06-20 6:24 UTC (permalink / raw)
To: Martin Jansa; +Cc: yocto@yoctoproject.org
>
> On Wed, Jun 18, 2014 at 07:30:49AM +0000, yaoxp@cn.fujitsu.com wrote:
> > Why not in oe-core?
> > What recipe can be put in oe-core, and what recipe can be put in meta-oe?
>
> "core" recipes which are used by most if not all OE builds
>
> "opt-in" extra recipes go to different "topic" layers
>
> nobody needed or asked for cim until now, so it's not "core" by this definition.
It is Development/Libraries in Fedora.
Why put in meta-networking?
----
$ rpm -qi cim-schema-2.33.0-6.fc20.noarch
Name : cim-schema
Version : 2.33.0
Release : 6.fc20
Architecture: noarch
Install Date: Wed 11 Jun 2014 03:24:18 PM CST
Group : Development/Libraries
Size : 6006252
License : DMTF
Signature : RSA/SHA256, Wed 07 Aug 2013 10:03:04 AM CST, Key ID 2eb161fa246110c1
Source RPM : cim-schema-2.33.0-6.fc20.src.rpm
Build Date : Sat 03 Aug 2013 01:08:10 PM CST
Build Host : arm02-builder20.arm.fedoraproject.org
Relocations : (not relocatable)
Packager : Fedora Project
Vendor : Fedora Project
URL : http://www.dmtf.org/
Summary : Common Information Model (CIM) Schema
Description :
Common Information Model (CIM) is a model for describing overall
management information in a network or enterprise environment. CIM
consists of a specification and a schema. The specification defines the
details for integration with other management models. The schema
provides the actual model descriptions.
Authors:
--------
DTMF <http://www.dmtf.org/about/contact>
>
> > > -----Original Message-----
> > > From: Burton, Ross [mailto:ross.burton@intel.com]
> > > Sent: Thursday, June 12, 2014 5:27 PM
> > > To: Yao, Xinpan
> > > Cc: yocto@yoctoproject.org
> > > Subject: Re: [yocto] [PATCH] add recipe cim-schema, cim-schema-docs
> > > and license file DMTF.
> > >
> > > On 12 June 2014 09:56, Martin Jansa <martin.jansa@gmail.com> wrote:
> > > > Why is this recipe needed in oe-core layer? Wouldn't
> > > > meta-networking be more suitable?
> > > >
> > > > The patch also belongs to oe-core ML not yocto.
> > >
> > > Agreed, unless there's a strong reason then this should go to
> > > meta-networking (so send to the openembedded-devel list).
> > >
> > > Ross
> > --
> > _______________________________________________
> > yocto mailing list
> > yocto@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/yocto
>
> --
> Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2014-06-20 6:24 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-06-12 3:26 [PATCH] add recipe cim-schema, cim-schema-docs and license file DMTF Yao Xinpan
2014-06-12 8:56 ` Martin Jansa
2014-06-12 9:27 ` Burton, Ross
2014-06-18 7:30 ` yaoxp
2014-06-18 7:54 ` Martin Jansa
2014-06-20 6:24 ` yaoxp
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.