Annotation of loncom/build/piml.dtd, revision 1.2

1.1       harris41    1: <!--
                      2:        Post Installation Markup Language version 1.0.
                      3: 
                      4:        Date: January 24, 2002
                      5:        Author: Scott Harrison
                      6: 
                      7:        Post Installation Markup Language works to perform
                      8:        'intelligent' modifications of existing files on
                      9:        a software system.  This allows for the reconfiguring
                     10:        of existing configuration files without having the
                     11:        overlap of files between software packages.  PIML
                     12:        also allows you to have file permission/ownership
                     13:        specifications different than that specified by the
                     14:        original software package.
                     15: 
                     16:        For instance, Apache web server configuration files
                     17:        are a popular target for many different software applications.
                     18:        A preferred approach is to simply append an 'Include ...'
                     19:        line to the Apache web server configuration files.
                     20: 
                     21:        Post Installation Markup Language is meant to be
                     22:        a natural wrapper to target installations generated
                     23:        by LPML (Linux Packaging Markup Language).
                     24: 
                     25:        Usages of Post Installation Markup Language are:
                     26:        * immediately after installation with LPML
                     27:        * generating '%post' syntax for RPMs
                     28:        * generating post-installation syntax for Debian packages.
                     29: 
                     30:        Dependency checking is supported as a poor man's probing....
                     31:        There is no point in reconfiguring a file that isn't installed,
                     32:        or is missing a system component for successful operation.
                     33: 
                     34:        Another neat use of PIML is to allow for invocation of various
                     35:        processes after installation.
                     36: -->
                     37: <!--
                     38: 
                     39: Copyright Michigan State University Board of Trustees
                     40: 
                     41: This file is part of the LearningOnline Network with CAPA (LON-CAPA).
                     42: 
                     43: LON-CAPA is free software; you can redistribute it and/or modify
                     44: it under the terms of the GNU General Public License as published by
                     45: the Free Software Foundation; either version 2 of the License, or
                     46: (at your option) any later version.
                     47: 
                     48: LON-CAPA is distributed in the hope that it will be useful,
                     49: but WITHOUT ANY WARRANTY; without even the implied warranty of
                     50: MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
                     51: GNU General Public License for more details.
                     52: 
                     53: You should have received a copy of the GNU General Public License
                     54: along with LON-CAPA; if not, write to the Free Software
                     55: Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
                     56: 
                     57: /home/httpd/html/adm/gpl.txt
                     58: 
                     59: http://www.lon-capa.org/
                     60: 
                     61: -->
                     62: 
                     63: <!ENTITY % piml.Version
                     64:         "-//TUX//DTD piml 1.0 Final//EN"
                     65: 
                     66:         -- Typical usage:
                     67: 
                     68:             <!DOCTYPE piml PUBLIC "-//TUX//DTD PIML 1.0 Final//EN">
                     69:             <piml>
                     70: 
                     71:             </piml>
                     72:         --
                     73:         >
                     74: 
                     75: <!ELEMENT categoryname (#PCDATA)>
                     76: <!ELEMENT targetroot (#PCDATA)>
                     77: 
                     78: <!ELEMENT target (#PCDATA)>
                     79: <!ATTLIST target
                     80:     dist CDATA #REQUIRED
                     81:     >
                     82: <!ELEMENT piml (specialnotices|files|categories)+>
                     83: <!ELEMENT specialnotices specialnotice+>
                     84: <!ELEMENT categories category+>
                     85: <!ELEMENT files (file)+>
                     86: <!ELEMENT dependencies (#PCDATA)>
                     87: <!ELEMENT note (#PCDATA)>
                     88: 
                     89: <!ELEMENT specialnotice (#PCDATA)>
                     90: <!ELEMENT category (chmod,chown,abbreviation)>
                     91: <!ATTLIST category
                     92:     type CDATA #REQUIRED
                     93:     name CDATA #REQUIRED
                     94:     >
                     95: <!ELEMENT chown (#PCDATA)>
                     96: <!ATTLIST chown
                     97:     dist CDATA #REQUIRED
                     98:     >
                     99: <!ELEMENT chmod (#PCDATA)>
                    100: <!ATTLIST chmod
                    101:     dist CDATA #REQUIRED
                    102:     >
                    103: <!ELEMENT abbreviation (#PCDATA)>
                    104: 
1.2     ! harris41  105: <!ELEMENT file (target,categoryname?,
1.1       harris41  106:                 note?,status?,dependencies?,perlscript)>
                    107: <!ELEMENT perlscript (#PCDATA)>

FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>