File:  [LON-CAPA] / loncom / build / piml.dtd
Revision 1.3: download - view: text, annotated - select for diffs
Sun Apr 14 20:35:25 2002 UTC (22 years, 2 months ago) by harris41
Branches: MAIN
CVS tags: version_2_9_X, version_2_9_99_0, version_2_9_1, version_2_9_0, version_2_8_X, version_2_8_99_1, version_2_8_99_0, version_2_8_2, version_2_8_1, version_2_8_0, version_2_7_X, version_2_7_99_1, version_2_7_99_0, version_2_7_1, version_2_7_0, version_2_6_X, version_2_6_99_1, version_2_6_99_0, version_2_6_3, version_2_6_2, version_2_6_1, version_2_6_0, version_2_5_X, version_2_5_99_1, version_2_5_99_0, version_2_5_2, version_2_5_1, version_2_5_0, version_2_4_X, version_2_4_99_0, version_2_4_2, version_2_4_1, version_2_4_0, version_2_3_X, version_2_3_99_0, version_2_3_2, version_2_3_1, version_2_3_0, version_2_2_X, version_2_2_99_1, version_2_2_99_0, version_2_2_2, version_2_2_1, version_2_2_0, version_2_1_X, version_2_1_99_3, version_2_1_99_2, version_2_1_99_1, version_2_1_99_0, version_2_1_3, version_2_1_2, version_2_1_1, version_2_1_0, version_2_12_X, version_2_11_X, version_2_11_4_uiuc, version_2_11_4_msu, version_2_11_4, version_2_11_3_uiuc, version_2_11_3_msu, version_2_11_3, version_2_11_2_uiuc, version_2_11_2_msu, version_2_11_2_educog, version_2_11_2, version_2_11_1, version_2_11_0_RC3, version_2_11_0_RC2, version_2_11_0_RC1, version_2_11_0, version_2_10_X, version_2_10_1, version_2_10_0_RC2, version_2_10_0_RC1, version_2_10_0, version_2_0_X, version_2_0_99_1, version_2_0_2, version_2_0_1, version_2_0_0, version_1_99_3, version_1_99_2, version_1_99_1_tmcc, version_1_99_1, version_1_99_0_tmcc, version_1_99_0, version_1_3_X, version_1_3_3, version_1_3_2, version_1_3_1, version_1_3_0, version_1_2_X, version_1_2_99_1, version_1_2_99_0, version_1_2_1, version_1_2_0, version_1_1_X, version_1_1_99_5, version_1_1_99_4, version_1_1_99_3, version_1_1_99_2, version_1_1_99_1, version_1_1_99_0, version_1_1_3, version_1_1_2, version_1_1_1, version_1_1_0, version_1_0_99_3, version_1_0_99_2, version_1_0_99_1, version_1_0_99, version_1_0_3, version_1_0_2, version_1_0_1, version_1_0_0, version_0_99_5, version_0_99_4, version_0_99_3, version_0_99_2, version_0_99_1, version_0_99_0, version_0_6_2, version_0_6, version_0_5_1, version_0_5, version_0_4, stable_2002_july, stable_2002_april, loncapaMITrelate_1, language_hyphenation_merge, language_hyphenation, conference_2003, bz6209-base, bz6209, bz5969, bz5610, bz2851, STABLE, PRINT_INCOMPLETE_base, PRINT_INCOMPLETE, HEAD, GCI_3, GCI_2, GCI_1, BZ5971-printing-apage, BZ5434-fox, BZ4492-merge, BZ4492-feature_horizontal_radioresponse, BZ4492-feature_Support_horizontal_radioresponse, BZ4492-Support_horizontal_radioresponse
fixing tags, attributes, doctype note and a few syntax things (now validates)

<!--
       Post Installation Markup Language version 1.0.

       Date: January 24, 2002
       Author: Scott Harrison

       Post Installation Markup Language works to perform
       'intelligent' modifications of existing files on
       a software system.  This allows for the reconfiguring
       of existing configuration files without having the
       overlap of files between software packages.  PIML
       also allows you to have file permission/ownership
       specifications different than that specified by the
       original software package.

       For instance, Apache web server configuration files
       are a popular target for many different software applications.
       A preferred approach is to simply append an 'Include ...'
       line to the Apache web server configuration files.

       Post Installation Markup Language is meant to be
       a natural wrapper to target installations generated
       by LPML (Linux Packaging Markup Language).

       Usages of Post Installation Markup Language are:
       * immediately after installation with LPML
       * generating '%post' syntax for RPMs
       * generating post-installation syntax for Debian packages.

       Dependency checking is supported as a poor man's probing....
       There is no point in reconfiguring a file that isn't installed,
       or is missing a system component for successful operation.

       Another neat use of PIML is to allow for invocation of various
       processes after installation.
-->
<!--

Copyright Michigan State University Board of Trustees

This file is part of the LearningOnline Network with CAPA (LON-CAPA).

LON-CAPA is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.

LON-CAPA is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
GNU General Public License for more details.

You should have received a copy of the GNU General Public License
along with LON-CAPA; if not, write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA

/home/httpd/html/adm/gpl.txt

http://www.lon-capa.org/

-->

<!ENTITY % piml.Version
        "-//TUX//DTD piml 1.0 Final//EN">

<!-- Typical usage:

            <!DOCTYPE piml PUBLIC "-//TUX//DTD PIML 1.0 Final//EN"
	    "http://lpml.sourceforge.net/DTD/piml.dtd">
            <piml>

            </piml>
 -->

<!ELEMENT categoryname (#PCDATA)>
<!ELEMENT targetroot (#PCDATA)>

<!ELEMENT target (#PCDATA)>
<!ATTLIST target
    dist CDATA #REQUIRED
    >
<!ELEMENT piml (targetroot|specialnotices|files|categories)+>
<!ELEMENT specialnotices (specialnotice)+>
<!ELEMENT categories (category)+>
<!ELEMENT files (file)+>
<!ELEMENT dependencies (#PCDATA)>
<!ATTLIST dependencies
    dist CDATA #REQUIRED
    >
<!ELEMENT note (#PCDATA)>

<!ELEMENT specialnotice (#PCDATA)>
<!ELEMENT category (chmod,chown,abbreviation)>
<!ATTLIST category
    type CDATA #REQUIRED
    name CDATA #REQUIRED
    >
<!ELEMENT chown (#PCDATA)>
<!ATTLIST chown
    dist CDATA #REQUIRED
    >
<!ELEMENT chmod (#PCDATA)>
<!ATTLIST chmod
    dist CDATA #REQUIRED
    >
<!ELEMENT abbreviation (#PCDATA)>

<!ELEMENT file (target,categoryname?,
                note?,status?,dependencies?,perlscript)>
<!ELEMENT TARGET EMPTY>
<!ELEMENT perlscript (#PCDATA|TARGET)*>
<!ATTLIST perlscript
    mode CDATA #REQUIRED
    >

FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>
500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at root@localhost to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.