summaryrefslogtreecommitdiffstats
path: root/meta/recipes-devtools/docbook-xml/docbook-xml-dtd4_4.5.bb
blob: 6452c8d99f72a406b1cb01fd3cd7c9fc772e4d09 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
SUMMARY = "Document type definitions for verification of XML data files"
DESCRIPTION = "Document type definitions for verification of XML data \
files against the DocBook rule set, it ships with the latest DocBook 4.5 \
XML DTD, as well as a selected set of legacy DTDs for use with older \
documents, including 4.0, 4.1.2, 4.2, 4.3 and 4.4"
HOMEPAGE = "http://www.docbook.org/xml/"

LICENSE = "OASIS"
LIC_FILES_CHKSUM = "file://${WORKDIR}/LICENSE-OASIS;md5=c608985dd5f7f215e669e7639a0b1d2e"

# Note: the upstream sources are not distributed with a license file.
# LICENSE-OASIS is included as a "patch" to workaround this. When
# upgrading this recipe, please verify whether this is still needed.
SRC_URI = "http://snapshot.debian.org/archive/debian/20160728T043443Z/pool/main/d/docbook-xml/docbook-xml_${PV}.orig.tar.gz \
           file://LICENSE-OASIS \
           file://docbook-xml-update-catalog.xml.patch \
"

SRC_URI[md5sum] = "487b4d44e15cffb1f4048af23f98208e"
SRC_URI[sha256sum] = "b0f8edcf697f5318e63dd98c9a931f3fee167af0805ba441db372e0f17b2a44f"

UPSTREAM_CHECK_URI = "${DEBIAN_MIRROR}/main/d/docbook-xml/"

S = "${WORKDIR}/docbook-xml-4.5.c31424"

inherit allarch
BBCLASSEXTEND = "native"

do_configure (){
    :
}

do_compile (){
    :
}

do_install () {
    install -d ${D}${sysconfdir}/xml/
    xmlcatalog --create --noout ${D}${sysconfdir}/xml/docbook-xml.xml

    for DTDVERSION in 4.0 4.1.2 4.2 4.3 4.4 4.5; do
        DEST=${datadir}/xml/docbook/schema/dtd/$DTDVERSION
        install -d -m 755 ${D}$DEST
        cp -v -R docbook-$DTDVERSION/* ${D}$DEST
        xmlcatalog --verbose --noout --add nextCatalog unused file://$DEST/catalog.xml ${D}${sysconfdir}/xml/docbook-xml.xml
    done
}

XMLCATALOGS = "${sysconfdir}/xml/docbook-xml.xml"
inherit xmlcatalog

FILES_${PN} = "${datadir}/* ${sysconfdir}/xml/docbook-xml.xml"
ully supports the target device hardware.</para></listitem> <listitem><para><filename>core-image-clutter</filename>: An image with support for the Open GL-based toolkit Clutter, which enables development of rich and animated graphical user interfaces.</para></listitem> <listitem><para><filename>core-image-full-cmdline</filename>: A console-only image with more full-featured Linux system functionality installed.</para></listitem> <listitem><para><filename>core-image-lsb</filename>: An image that conforms to the Linux Standard Base (LSB) specification. This image requires a distribution configuration that enables LSB compliance (e.g. <filename>poky-lsb</filename>). If you build <filename>core-image-lsb</filename> without that configuration, the image will not be LSB-compliant. </para></listitem> <listitem><para><filename>core-image-lsb-dev</filename>: A <filename>core-image-lsb</filename> image that is suitable for development work using the host. The image includes headers and libraries you can use in a host development environment. This image requires a distribution configuration that enables LSB compliance (e.g. <filename>poky-lsb</filename>). If you build <filename>core-image-lsb-dev</filename> without that configuration, the image will not be LSB-compliant. </para></listitem> <listitem><para><filename>core-image-lsb-sdk</filename>: A <filename>core-image-lsb</filename> that includes everything in the cross-toolchain but also includes development headers and libraries to form a complete standalone SDK. This image requires a distribution configuration that enables LSB compliance (e.g. <filename>poky-lsb</filename>). If you build <filename>core-image-lsb-sdk</filename> without that configuration, the image will not be LSB-compliant. This image is suitable for development using the target.</para></listitem> <listitem><para><filename>core-image-minimal</filename>: A small image just capable of allowing a device to boot.</para></listitem> <listitem><para><filename>core-image-minimal-dev</filename>: A <filename>core-image-minimal</filename> image suitable for development work using the host. The image includes headers and libraries you can use in a host development environment. </para></listitem> <listitem><para id='images-core-image-minimal-initramfs'><filename>core-image-minimal-initramfs</filename>: A <filename>core-image-minimal</filename> image that has the Minimal RAM-based Initial Root Filesystem (initramfs) as part of the kernel, which allows the system to find the first “init” program more efficiently. See the <link linkend='var-PACKAGE_INSTALL'><filename>PACKAGE_INSTALL</filename></link> variable for additional information helpful when working with initramfs images. </para></listitem> <listitem><para><filename>core-image-minimal-mtdutils</filename>: A <filename>core-image-minimal</filename> image that has support for the Minimal MTD Utilities, which let the user interact with the MTD subsystem in the kernel to perform operations on flash devices. </para></listitem> <listitem><para><filename>core-image-rt</filename>: A <filename>core-image-minimal</filename> image plus a real-time test suite and tools appropriate for real-time use.</para></listitem> <listitem><para><filename>core-image-rt-sdk</filename>: A <filename>core-image-rt</filename> image that includes everything in the cross-toolchain. The image also includes development headers and libraries to form a complete stand-alone SDK and is suitable for development using the target. </para></listitem> <listitem><para><filename>core-image-sato</filename>: An image with Sato support, a mobile environment and visual style that works well with mobile devices. The image supports X11 with a Sato theme and applications such as a terminal, editor, file manager, media player, and so forth. </para></listitem> <listitem><para><filename>core-image-sato-dev</filename>: A <filename>core-image-sato</filename> image suitable for development using the host. The image includes libraries needed to build applications on the device itself, testing and profiling tools, and debug symbols. This image was formerly <filename>core-image-sdk</filename>. </para></listitem> <listitem><para><filename>core-image-sato-sdk</filename>: A <filename>core-image-sato</filename> image that includes everything in the cross-toolchain. The image also includes development headers and libraries to form a complete standalone SDK and is suitable for development using the target.</para></listitem> <listitem><para><filename>core-image-testmaster</filename>: A "master" image designed to be used for automated runtime testing. Provides a "known good" image that is deployed to a separate partition so that you can boot into it and use it to deploy a second image to be tested. You can find more information about runtime testing in the "<ulink url='&YOCTO_DOCS_DEV_URL;#performing-automated-runtime-testing'>Performing Automated Runtime Testing</ulink>" section in the Yocto Project Development Tasks Manual. </para></listitem> <listitem><para><filename>core-image-testmaster-initramfs</filename>: A RAM-based Initial Root Filesystem (initramfs) image tailored for use with the <filename>core-image-testmaster</filename> image. </para></listitem> <listitem><para><filename>core-image-weston</filename>: A very basic Wayland image with a terminal. This image provides the Wayland protocol libraries and the reference Weston compositor. For more information, see the "<ulink url='&YOCTO_DOCS_DEV_URL;#dev-using-wayland-and-weston'>Using Wayland and Weston</ulink>" section in the Yocto Project Development Tasks Manual. </para></listitem> <listitem><para><filename>core-image-x11</filename>: A very basic X11 image with a terminal. </para></listitem> </itemizedlist> </para> </chapter> <!-- vim: expandtab tw=80 ts=4 -->