• Login
    • Report A Bug
    • System Information
    • System Tests
    • System Policies
    • Code Documentation
    • Occam Source Code
    • Web Client Source Code
    • About Occam
    • Acknowledgements
    • Guides / Documentation
    • Publications

translation missing: en.flash.saving
translation missing: en.flash.error
  • Bibliography Data
  • Metadata
data
    docbook-xsl1.79.2
    QmWiGHKkQ5ee8b24wv8USsWBz4D77P8MyZSSt83Vm7wzbJ
    5dsL7LqDq4b6TE7uBmyhcVgvukyMKj
      QmWiGHKkQ5ee8b24wv8USsWBz4D77P8MyZSSt83Vm7wzbJ
      5dsL7LqDq4b6TE7uBmyhcVgvukyMKj

      • Details
      • Build
      • Files
      • History
        • Website

          http://docbook.org/

          License

          • custom

          Environment

          linux

          Architecture

          x86-64

          DocBook is a schema (available in several languages including RELAX NG, SGML and XML DTDs, and W3C XML Schema) maintained by the DocBook Technical Committee of OASIS. It is particularly well suited to books and papers about computer hardware and software (though it is by no means limited to these applications).

          Because it is a large and robust schema, and because its main structures correspond to the general notion of what constitutes a “book,” DocBook has been adopted by a large and growing community of authors writing books of all kinds. DocBook is supported “out of the box” by a number of commercial tools, and there is rapidly expanding support for it in a number of free software environments. These features have combined to make DocBook a generally easy to understand, widely useful, and very popular schema. Dozens of organizations are using DocBook for millions of pages of documentation, in various print and online formats, worldwide.

          Versions

          • 1.79.2

          • 1.79.2.1

          Related

          • maintainer

            occam

          DependenciesHelp

          This section shows a list of objects the current object is dependent upon in order to be used.

          For dependencies that are only relevant as part of the build or runtime of the object, it is best to describe those local to those sections.

          • library

            xml2

            2.x

          • library

            xslt

            1.x

          • data

            docbook-xml

            4.x

          BuildHelp

          This section tracks information useful to describing how to build this object.

          Dependencies

          • collection

            build

            1.0

          Resources

          • docbook-xsl-nons-1.79.2.tar.gz

            application/gzip

            docbook xslt10-stylesheets 1.79.2 Release

            https://github.com/docbook/xslt10-stylesheets/releases/download/release%2F1.79.2/docbook-xsl-nons-1.79.2.tar.gz

            QmSppWXwWwk7LyZtRF4LJHuyzjxyUFpujVM1XYHjgBXqTu

            Qmb6gZAf3qQELPJwDSxXtQCudbdvxb3qrqWMzm5j2vwEbP

            Qmf4zqifvHrik9xJQA79kP7VACUCC5ZhEhK3gYeY6TEoY9

            download

          Command

          • /bin/bash
          • build.sh

          Build Environment

          • linux
          • x86-64

          InstallationHelp

          Objects have a set of files that comprise that object, as seen in the Files tab. When an object is built, they have a set of files that are the result of that build. In each case, these sets of files are the ones that are accessible within a virtual machine when running the object.

          This section describes how those files are accessible and visible to that machine. When a virtual machine is created, the data is always accessible read-only within a particular mounted directory. However, applications may expect to be located at particular directories. This section allows one to place files in different directories when the virtual machine is launched.

          There are two types of access. One is a link where the file is not copied from its original location. Instead, it creates what is called a symbolic link which is a "shortcut" that acts like a normal file but allows the actual data to be in a different directory. The other type is a traditional copy which copies the data explicitly to the provided destination. This takes more time, but the copy can be modified, unlike the read-only link type.

          ActionSourceDestinationSummary
          Linkusr/lib/usr/lib

          N/A

          Linkusr/include/usr/include

          N/A

          Linkusr/share/usr/share

          N/A

          Linkusr/bin/usr/bin

          N/A

          Linketc/etc

          N/A

          No files will be installed.

          Share

          • URL

            Copy
          • Embed Link

            Copy
          • QR Code

        • JavaScript must be enabled.

          There was an error retrieving this content.

          The content could not be found.

        • JavaScript must be enabled.

          There was an error retrieving this content.

          The content could not be found.

        • JavaScript must be enabled.

          There was an error retrieving this content.

          The content could not be found.

        Confirm
        Do you wish to proceed?

        Confirm message?