debian/0000755000000000000000000000000012142700134007160 5ustar debian/clean0000644000000000000000000000021711574737366010216 0ustar doc/*.xml doc/*.html doc/*.n README README.html TclxmlConfig.sh config.log config.status config.status.lineno Makefile include/tclxml/tclxml.h debian/rules0000755000000000000000000000106612142677141010256 0ustar #!/usr/bin/make -f %: dh $@ --with=autoreconf override_dh_auto_configure: dh_auto_configure -- --with-tcl=/usr/lib/ --enable-threads --enable-shared override_dh_auto_install: dh_auto_install $(MAKE) doc override_dh_install: dh_install find debian/tclxml -depth -type d -empty -exec rmdir {} \; override_dh_auto_test: override_dh_shlibdeps: dh_shlibdeps tcltk-depends .PHONY: get-orig-source override_dh_auto_configure override_dh_auto_install override_dh_install override_dh_auto_test override_dh_shlibdeps get-orig-source: debian/get-orig-source.sh debian/watch0000644000000000000000000000033011550651605010217 0ustar version=3 opts=uversionmangle=s/\.(tar.*|tgz|zip|gz|bz2)$//i,dversionmangle=s/[-.+~]?(cvs|svn|git|snapshot|pre|hg)(.*)$//i,pasv \ http://sf.net/tclxml/tclxml-?_?([\d+\.]+|\d+)\.(tar.*|tgz|zip|gz|bz2|) debian uupdate debian/patches/0000755000000000000000000000000011737653366010636 5ustar debian/patches/01-fix-tcllibpath.diff0000644000000000000000000000202011550651605014575 0ustar Description: Fix the TCLLIBPATH to generate missing docs Author: Andrew O. Shadoura diff --git a/Makefile.in b/Makefile.in --- a/Makefile.in +++ b/Makefile.in @@ -135,7 +135,7 @@ EXTRA_PATH = $(top_builddir):$(TCL_BIN_DIR) #EXTRA_PATH = $(top_builddir):$(TCL_BIN_DIR):$(TK_BIN_DIR) -TCLLIBPATH = $(top_builddir) +TCLLIBPATH = $(CURDIR)/debian/tmp/usr/lib/Tclxml3.3 TCLSH_ENV = TCL_LIBRARY=`@CYGPATH@ $(TCL_SRC_DIR)/library` \ @LD_LIBRARY_PATH_VAR@="$(EXTRA_PATH):$(@LD_LIBRARY_PATH_VAR@)" \ PATH="$(EXTRA_PATH):$(PATH)" \ @@ -212,7 +212,7 @@ -$(TCLSH) doc/transform.tcl doc/tclxslt.xml doc/html.xsl doc/tclxslt.html -$(TCLSH) doc/transform.tcl doc/tclxslt.xml doc/nroff.xsl doc/tclxslt.n -$(TCLSH) doc/transform.tcl doc/README.xml doc/html.xsl README.html - -$(TCLSH) doc/transform.tcl doc/README.xml doc/txt.xsl -o README + -$(TCLSH) doc/transform.tcl doc/README.xml doc/txt.xsl README # Do not install the documentation by default, # since it may not have been built (see above). debian/patches/series0000644000000000000000000000010211737653372012041 0ustar 01-fix-tcllibpath.diff 02-fix-manpages.diff 03-hurd-kfreebsd.diff debian/patches/03-hurd-kfreebsd.diff0000644000000000000000000000050311737653366014433 0ustar Description: Fix build on GNU/Hurd and GNU/kFreeBSD --- pgtcl-1.5.orig/tclconfig/tcl.m4 +++ pgtcl-1.5/tclconfig/tcl.m4 @@ -1218,7 +1218,7 @@ dnl AC_CHECK_TOOL(AR, ar, :) fi fi ;; - Linux*) + Linux*|GNU*|NetBSD-Debian) SHLIB_CFLAGS="-fPIC" SHLIB_LD_LIBS='${LIBS}' SHLIB_SUFFIX=".so" debian/patches/02-fix-manpages.diff0000644000000000000000000015041311735147133014256 0ustar Description: Fix manpages generation Author: Andrew O. Shadoura --- a/doc/tcldom.xml.in +++ b/doc/tcldom.xml.in @@ -26,25 +26,10 @@ TclDOM - n + 3tcl - ::dom::DOMImplementation - ::dom::hasfeature - ::dom::create - ::dom::destroy - ::dom::parse - ::dom::serialize - ::dom::document - ::dom::documenttype - ::dom::node - ::dom::element - ::dom::event - ::dom::selectNode - ::dom::isNode - ::dom::xinclude - ::dom::prefix2namespaceURI - ::dom::trim + TclDOM Tcl language binding for the W3C Document Object Model --- a/doc/tclxml.xml.in +++ b/doc/tclxml.xml.in @@ -44,7 +44,7 @@ TclXML - n + 3tcl TclXML --- a/doc/tclxslt.xml.in +++ b/doc/tclxslt.xml.in @@ -1 +1 @@ - ]> Steve Ball 2009 2008 2007 2005 Explain 2004 2003 2002 Zveno Pty Ltd See the file LICENSE for information on usage and redistribution of this file, and for a DISCLAIMER OF ALL WARRANTIES. TclXSLT n ::xslt::compile ::xslt::extension ::xslt::security package require xslt xslt &version; ::xslt ::xslt::compile doc ssheet method option value args ::xslt::extension add nsuri tcl-namespace ::xslt::security request detail Description TclXSLT is a wrapper for the Gnome libxslt library that allows an application to perform XSL transformations (XSLT). The package also provides a binding to the XSLT extension mechanism so that XSLT extension may be implemented using Tcl scripts. Transformation only works with documents created by TclDOM/libxml2. The TclXSLT package makes extensive use of Tcl objects. Compiled XSL stylesheets are stored as the internal representation of a Tcl object. Source and result documents are accessed via TclDOM's C interface as Tcl objects. This allows the application to cache parsed XML documents and compiled XSL stylesheets for better runtime performance. Packages and Namespaces The TclXSLT package defines the xslt package and also a Tcl namespace using that name. Commands ::xslt::compile The ::xslt::compile command compiles a stylesheet document. It returns a compiled stylesheet object and also defines a Tcl command to access the stylesheet. This Tcl command may be used to transform XML documents. Example set source_doc [::dom::libxml2::parse $XML] set ssheet_doc [::dom::libxml2::parse $XSLstylesheet] set ssheet [::xslt::compile $ssheet_doc] set result [$ssheet transform $source_doc] NB. It is advisable to use the option when parsing the source and stylesheet documents to allow external resources to be resolved. Stylesheet Command The stylesheet command created by ::xslt::compile command accesses a compiled stylesheet. Command Methods The following command methods may be used: cget option Returns the value of an option. See below for the list of valid options. configure option value Sets the value of an option. Available options are as follows: Specifies whether the output being produced by the stylesheet should be idented (or "pretty-printed"). This is usually set by the styesheet's xsl:output element. The result is a boolean value. This is a read-only option. script This option specifies a Tcl command to be evaluated when a message is produced by the stylesheet. Messages may be produced when the stylesheet detects an error during processing, or when the stylesheet uses the xsl:message element. It is currently not possible to distinguish between an error message and a message produced using xsl:message. Specifies the output being produced by the stylesheet. This is usually set by the styesheet's xsl:output element. May have the value xml, html, xhtml, text or an empty string. If the result is an empty string, then the output method used depends on the type of the result document. If the result document is of type "HTML" (ie. if [dom::node cget $resultdoc -nodeType] returns HTMLdocument), then the html output method should be used. Otherwise the output method to use is xml. This is a read-only option. Specifies the name of a channel into which profiling information is written. The channel must have been opened for writing, or an error will be returned when attempting a transformation. Only file channels may be used and only on Unix systems. Specifies the target URI for the transformation, ie. where the result will be written to. The result document is not written to this URI automatically; the application should write the result document to this URI itself. Some transformation constructs resolve relative URIs against this URI. For example, a subsidiary result document produced using the document element. get what Returns information from the stylesheet. The following values may be used for what: parameters Returns a Tcl list describing the parameters that the stylesheet accepts. Each member of the list is itself a Tcl list with three members: {name ns select}. name is the name of the parameter, ns is the XML namespace for the parameter and select is the value of the select attribute of the param element, if any (ie. the default value of the parameter). This implementation is not able to return a default value set using the content of the param element. All stylesheet parameters are returned by this method, including those in included/imported stylesheets. Where more than one parameter is defined with the same name, only the parameter with the highest import precedence is included in the returned list. transform source name value Performs an XSL transformation on the given source document. Stylesheet parameters may be specified as name-value pairs. The return result is the DOM token for the result document. Stylesheet Parameters Any number of name-value pairs may be specified as arguments to the stylesheet transform method. These are passed as values for parameters in the stylesheet. libxslt interprets the values as XPath expressions, where the context node is the root node for the source document. To pass a value as a string it must be XPath-quoted, for example set library "Gnome libxslt" $ssheet transform $source_doc \ library '$library' \ author "'Daniel Veillard'" \ node {/*/Element[3]} Following is an example of how to use the stylesheet transform method. Example set source_doc [::dom::libxml2::parse $XML] set ssheet_doc [::dom::libxml2::parse $XSLstylesheet] set ssheet [::xslt::compile $ssheet_doc] set result_doc [$ssheet transform $source_doc] set result_xml [::dom::libxml2::serialize $result_doc \ -method [$ssheet cget -method]] ::xslt::extension The ::xslt::extension command is used to manage extensions of the libxslt library. The add is used to register an extension. The remove is used to unregister an extension. See EXTENSIONS for more detail. ::xslt::security The ::xslt::security command is a "call-in" used to manage the security of a stylesheet performing a transformation. The TclXSLT package does not create this command. A stylesheet may need to perform an operation on an external resource, such as reading or writing a file, or opening a network connection. Before performing such an operation, TclXSLT will invoke the ::xslt::security command. It interprets the result of the command as a boolean value, and only if the "true" value is returned will it instruct the libxslt library to continue. TclXSLT will invoke the ::xslt::security command in a different fashion depending on whether the current interpreter is safe or unsafe. If the current interpeter is unsafe (ie. it is a trusted interpreter) then the command is invoked in the usual manner (see below for arguments). If the command does not exist then the value "true" is the default, ie. the operation will be permitted. If the current interpreter is safe then the command is invoked as a hidden command. This is to ensure that the untrusted script cannot intercept the invocation of the command. If the hidden command does not exist then the value "false" is the default, ie. the operation will not be permitted. When the ::xslt::security command is invoked two arguments are appended: ::xslt::security request detail request This indicates the operation being requested and may have one of the following values: readfile Extensions The TclXSLT package allows an application to bind Tcl scripts to the extension mechanism of libxslt. This means that Tcl scripts may provide the implementation of an XSLT extension element or function. The binding is achieved to associating a Tcl namespace with an XML namespace. Implementing An Extension The Tcl application uses the ::xslt::extension add command to register an extension. An XML Namespace for the extension is specified as an argument, along with a Tcl namespace that will provide implementations of extension elements and functions. For example, ::xslt::extension add http://tclxml.sourceforge.net/Example ::example Everytime the ::xslt::transform command is executed, a newly-created XSLT engine is initialized. For each registered extension, every procedure in the associated Tcl namespace is defined in the XSLT engine as either an extension element or an extension function. The procedure is defined as an extension function if it has a variable argument list, otherwise it is defined as an extension element. The procedure name is used as the local part of the extension name. For example, namespace eval example { namespace export myfunc myelement } proc example::myfunc {name args} { global app return $app($name) } proc example::myelement {content node inst avts} { global app puts $app([dom::libxml2::node cget $node -nodeName]) return {} } "myfunc" is defined as an extension function and "myelement" is defined as an extension element. Extension Functions The arguments to an extension function are passed as parameters to the Tcl procedure. Each argument may be passed as a string or as a nodeset. Nodesets are presented as TclDOM nodes. The return result of the Tcl procedure becomes the return value of the extension function. The type of the result is preserved where possible, otherwise it is converted to a string value. Extension Elements When an extension element associated with a registered namespace is instantiated all attributes of the extension element are evaluated as Attribute Value Templates and the content of the extension element is evaluated as a sequence constructor. The Tcl procedure associated with the extension element is then invoked. The Tcl procedure is passed four parameters: The first parameter is a DOM document, an RVT, that is the result of the sequence constructor. The second parameter is the current node in the source document. The third parameter is the extension element in the stylesheet document. The fourth parameter is a list. Each element in the list represents an attribute of the extension element. The list elements are each a sublist that has three values: Attribute name Attribute XML namespace Attribute value after evaluation as an AVT Any result returned by the Tcl procedure is discarded (in the current implementation). If the Tcl procedure raises an error then this is passed through to the XSL stylesheet as an XSLT exception condition. Using An Extension To invoke an extension in an XSL stylesheet, use the normal XSLT extension mechanism. The XML Namespace matches the extension to the registered Tcl namespace (NB. the stylesheet author is free to choose any prefix for the extension namespace). For example, <xsl:stylesheet version='1.0' xmlns:xsl='http://www.w3.org/1999/XSL/Transform' xmlns:eg='http://tclxml.sourceforge.net/Example'> <xsl:template match='/'> <xsl:text>Result of calling extension is "</xsl:text> <xsl:value-of select='eg:myfunc("foo")'/> <xsl:text>". </xsl:text> </xsl:template> </xsl:stylesheet> This stylesheet would result in the following Tcl script being evaluated: ::example::myfunc foo \ No newline at end of file + ]> Steve Ball 2009 2008 2007 2005 Explain 2004 2003 2002 Zveno Pty Ltd See the file LICENSE for information on usage and redistribution of this file, and for a DISCLAIMER OF ALL WARRANTIES. TclXSLT 3tcl TclXSLT XSLT support for Tcl package require xslt xslt &version; ::xslt ::xslt::compile doc ssheet method option value args ::xslt::extension add nsuri tcl-namespace ::xslt::security request detail Description TclXSLT is a wrapper for the Gnome libxslt library that allows an application to perform XSL transformations (XSLT). The package also provides a binding to the XSLT extension mechanism so that XSLT extension may be implemented using Tcl scripts. Transformation only works with documents created by TclDOM/libxml2. The TclXSLT package makes extensive use of Tcl objects. Compiled XSL stylesheets are stored as the internal representation of a Tcl object. Source and result documents are accessed via TclDOM's C interface as Tcl objects. This allows the application to cache parsed XML documents and compiled XSL stylesheets for better runtime performance. Packages and Namespaces The TclXSLT package defines the xslt package and also a Tcl namespace using that name. Commands ::xslt::compile The ::xslt::compile command compiles a stylesheet document. It returns a compiled stylesheet object and also defines a Tcl command to access the stylesheet. This Tcl command may be used to transform XML documents. Example set source_doc [::dom::libxml2::parse $XML] set ssheet_doc [::dom::libxml2::parse $XSLstylesheet] set ssheet [::xslt::compile $ssheet_doc] set result [$ssheet transform $source_doc] NB. It is advisable to use the option when parsing the source and stylesheet documents to allow external resources to be resolved. Stylesheet Command The stylesheet command created by ::xslt::compile command accesses a compiled stylesheet. Command Methods The following command methods may be used: cget option Returns the value of an option. See below for the list of valid options. configure option value Sets the value of an option. Available options are as follows: Specifies whether the output being produced by the stylesheet should be idented (or "pretty-printed"). This is usually set by the styesheet's xsl:output element. The result is a boolean value. This is a read-only option. script This option specifies a Tcl command to be evaluated when a message is produced by the stylesheet. Messages may be produced when the stylesheet detects an error during processing, or when the stylesheet uses the xsl:message element. It is currently not possible to distinguish between an error message and a message produced using xsl:message. Specifies the output being produced by the stylesheet. This is usually set by the styesheet's xsl:output element. May have the value xml, html, xhtml, text or an empty string. If the result is an empty string, then the output method used depends on the type of the result document. If the result document is of type "HTML" (ie. if [dom::node cget $resultdoc -nodeType] returns HTMLdocument), then the html output method should be used. Otherwise the output method to use is xml. This is a read-only option. Specifies the name of a channel into which profiling information is written. The channel must have been opened for writing, or an error will be returned when attempting a transformation. Only file channels may be used and only on Unix systems. Specifies the target URI for the transformation, ie. where the result will be written to. The result document is not written to this URI automatically; the application should write the result document to this URI itself. Some transformation constructs resolve relative URIs against this URI. For example, a subsidiary result document produced using the document element. get what Returns information from the stylesheet. The following values may be used for what: parameters Returns a Tcl list describing the parameters that the stylesheet accepts. Each member of the list is itself a Tcl list with three members: {name ns select}. name is the name of the parameter, ns is the XML namespace for the parameter and select is the value of the select attribute of the param element, if any (ie. the default value of the parameter). This implementation is not able to return a default value set using the content of the param element. All stylesheet parameters are returned by this method, including those in included/imported stylesheets. Where more than one parameter is defined with the same name, only the parameter with the highest import precedence is included in the returned list. transform source name value Performs an XSL transformation on the given source document. Stylesheet parameters may be specified as name-value pairs. The return result is the DOM token for the result document. Stylesheet Parameters Any number of name-value pairs may be specified as arguments to the stylesheet transform method. These are passed as values for parameters in the stylesheet. libxslt interprets the values as XPath expressions, where the context node is the root node for the source document. To pass a value as a string it must be XPath-quoted, for example set library "Gnome libxslt" $ssheet transform $source_doc \ library '$library' \ author "'Daniel Veillard'" \ node {/*/Element[3]} Following is an example of how to use the stylesheet transform method. Example set source_doc [::dom::libxml2::parse $XML] set ssheet_doc [::dom::libxml2::parse $XSLstylesheet] set ssheet [::xslt::compile $ssheet_doc] set result_doc [$ssheet transform $source_doc] set result_xml [::dom::libxml2::serialize $result_doc \ -method [$ssheet cget -method]] ::xslt::extension The ::xslt::extension command is used to manage extensions of the libxslt library. The add is used to register an extension. The remove is used to unregister an extension. See EXTENSIONS for more detail. ::xslt::security The ::xslt::security command is a "call-in" used to manage the security of a stylesheet performing a transformation. The TclXSLT package does not create this command. A stylesheet may need to perform an operation on an external resource, such as reading or writing a file, or opening a network connection. Before performing such an operation, TclXSLT will invoke the ::xslt::security command. It interprets the result of the command as a boolean value, and only if the "true" value is returned will it instruct the libxslt library to continue. TclXSLT will invoke the ::xslt::security command in a different fashion depending on whether the current interpreter is safe or unsafe. If the current interpeter is unsafe (ie. it is a trusted interpreter) then the command is invoked in the usual manner (see below for arguments). If the command does not exist then the value "true" is the default, ie. the operation will be permitted. If the current interpreter is safe then the command is invoked as a hidden command. This is to ensure that the untrusted script cannot intercept the invocation of the command. If the hidden command does not exist then the value "false" is the default, ie. the operation will not be permitted. When the ::xslt::security command is invoked two arguments are appended: ::xslt::security request detail request This indicates the operation being requested and may have one of the following values: readfile Extensions The TclXSLT package allows an application to bind Tcl scripts to the extension mechanism of libxslt. This means that Tcl scripts may provide the implementation of an XSLT extension element or function. The binding is achieved to associating a Tcl namespace with an XML namespace. Implementing An Extension The Tcl application uses the ::xslt::extension add command to register an extension. An XML Namespace for the extension is specified as an argument, along with a Tcl namespace that will provide implementations of extension elements and functions. For example, ::xslt::extension add http://tclxml.sourceforge.net/Example ::example Everytime the ::xslt::transform command is executed, a newly-created XSLT engine is initialized. For each registered extension, every procedure in the associated Tcl namespace is defined in the XSLT engine as either an extension element or an extension function. The procedure is defined as an extension function if it has a variable argument list, otherwise it is defined as an extension element. The procedure name is used as the local part of the extension name. For example, namespace eval example { namespace export myfunc myelement } proc example::myfunc {name args} { global app return $app($name) } proc example::myelement {content node inst avts} { global app puts $app([dom::libxml2::node cget $node -nodeName]) return {} } "myfunc" is defined as an extension function and "myelement" is defined as an extension element. Extension Functions The arguments to an extension function are passed as parameters to the Tcl procedure. Each argument may be passed as a string or as a nodeset. Nodesets are presented as TclDOM nodes. The return result of the Tcl procedure becomes the return value of the extension function. The type of the result is preserved where possible, otherwise it is converted to a string value. Extension Elements When an extension element associated with a registered namespace is instantiated all attributes of the extension element are evaluated as Attribute Value Templates and the content of the extension element is evaluated as a sequence constructor. The Tcl procedure associated with the extension element is then invoked. The Tcl procedure is passed four parameters: The first parameter is a DOM document, an RVT, that is the result of the sequence constructor. The second parameter is the current node in the source document. The third parameter is the extension element in the stylesheet document. The fourth parameter is a list. Each element in the list represents an attribute of the extension element. The list elements are each a sublist that has three values: Attribute name Attribute XML namespace Attribute value after evaluation as an AVT Any result returned by the Tcl procedure is discarded (in the current implementation). If the Tcl procedure raises an error then this is passed through to the XSL stylesheet as an XSLT exception condition. Using An Extension To invoke an extension in an XSL stylesheet, use the normal XSLT extension mechanism. The XML Namespace matches the extension to the registered Tcl namespace (NB. the stylesheet author is free to choose any prefix for the extension namespace). For example, <xsl:stylesheet version='1.0' xmlns:xsl='http://www.w3.org/1999/XSL/Transform' xmlns:eg='http://tclxml.sourceforge.net/Example'> <xsl:template match='/'> <xsl:text>Result of calling extension is "</xsl:text> <xsl:value-of select='eg:myfunc("foo")'/> <xsl:text>". </xsl:text> </xsl:template> </xsl:stylesheet> This stylesheet would result in the following Tcl script being evaluated: ::example::myfunc foo --- a/doc/nroff.xsl +++ b/doc/nroff.xsl @@ -88,8 +88,7 @@ - .BS -'\" Note: do not modify the .SH NAME line immediately below! + '\" Note: do not modify the .SH NAME line immediately below! .SH NAME @@ -99,7 +98,6 @@ \- -.BE debian/tclxml.manpages0000644000000000000000000000001011550651605012201 0ustar doc/*.n debian/README.Debian0000644000000000000000000000026711550651605011240 0ustar tclxml for Debian ----------------- This is the main parser that is built with plain old ./configure ; make -- David N. Welton , Wed, 18 Dec 2002 12:16:22 -0800 debian/copyright0000644000000000000000000000257211676632342011141 0ustar This package was debianized by David N. Welton on Wed, 18 Dec 2002 12:16:22 -0800. It was downloaded from http://tclxml.sourceforge.net Current maintainer: Andrew O. Shadura Upstream Author: Steve Ball Copyright: Copyright (c) 1998-2002 Zveno Pty Ltd http://www.zveno.com/ Zveno makes this software available free of charge for any purpose. Copies may be made of this software but all of this notice must be included on any copy. The software was developed for research purposes only and Zveno does not warrant that it is error free or fit for any purpose. Zveno disclaims any liability for all claims, expenses, losses, damages and costs any user may incur as a result of using, copying or modifying this software. Copyright (c) 1997 ANU and CSIRO on behalf of the participants in the CRC for Advanced Computational Systems ('ACSys'). ACSys makes this software and all associated data and documentation ('Software') available free of charge for any purpose. You may make copies of the Software but you must include all of this notice on any copy. The Software was developed for research purposes and ACSys does not warrant that it is error free or fit for any purpose. ACSys disclaims any liability for all claims, expenses, losses, damages and costs any user may incur as a result of using, copying or modifying the Software. debian/get-orig-source.sh0000755000000000000000000000111111704222565012536 0ustar #!/bin/sh UPSTREAM_REPO=http://tclxml.svn.sourceforge.net/svnroot/tclxml/trunk PACKAGE=tclxml SRC_VERSION=$(dpkg-parsechangelog | sed -ne 's/^Version: \(\([0-9]\+\):\)\?\(.*\)-.*/\3/p') SVN_REVISION=${SRC_VERSION##*svn} TARBALL=${PACKAGE}_${SRC_VERSION}.orig.tar.gz rm -rf debian/orig-source mkdir debian/orig-source svn export -r ${SVN_REVISION} ${UPSTREAM_REPO} debian/orig-source/${PACKAGE}-${SRC_VERSION}.orig || exit GZIP='--best --no-name' tar --owner=root --group=root --mode=a+rX czf ${TARBALL} -C debian/orig-source ${PACKAGE}-${SRC_VERSION}.orig rm -rf debian/orig-source debian/doc-base0000644000000000000000000000042211735140124010562 0ustar Document: tclxml Title: TclXML, TclXSLT and TclDOM manual page Author: Steve Ball Abstract: This manual describes what tclxml package is, and how it can be used. Section: Programming Format: HTML Index: /usr/share/doc/tclxml/README.html Files: /usr/share/doc/tclxml/*.html debian/tclxml.examples0000644000000000000000000000001311550651605012227 0ustar examples/* debian/compat0000644000000000000000000000000211550651605010370 0ustar 7 debian/tclxml.docs0000644000000000000000000000003611550651605011346 0ustar README README.html doc/*.html debian/tclxml.install0000644000000000000000000000003711550651605012065 0ustar /usr/lib/*/*so /usr/lib/*/*tcl debian/control0000644000000000000000000000240212142677317010601 0ustar Source: tclxml Section: devel Priority: optional Maintainer: Andrew Shadura Homepage: http://tclxml.sourceforge.net/ Build-Depends: debhelper (>= 7.0.50~), dh-autoreconf, automake, tcl-dev, libxml2-dev, libxslt1-dev, expat, tcllib Standards-Version: 3.9.3 Vcs-hg: http://anonscm.debian.org/hg/collab-maint/tclxml/ Vcs-Browser: http://anonscm.debian.org/hg/collab-maint/tclxml/summary Package: tclxml Architecture: any Depends: ${misc:Depends}, ${shlibs:Depends}, ${tcl:Depends}, tcllib Description: Tcl library for XML parsing TclXML provides event-based parsing of XML documents. The application may register callback scripts for certain document features, and when the parser encounters those features while parsing the document the callback is evaluated. Package: tclxml-dev Section: libdevel Architecture: any Depends: tclxml (= ${binary:Version}), ${misc:Depends}, ${tcl:Depends} Description: Tcl library for XML parsing - development files TclXML provides event-based parsing of XML documents. The application may register callback scripts for certain document features, and when the parser encounters those features while parsing the document the callback is evaluated. . This package contains files needed for C development with tclxml. debian/changelog0000644000000000000000000000713112142677660011055 0ustar tclxml (3.3~svn11-3) unstable; urgency=low * Fix FTBFS (Closes: #707515). * Adjust Vcs-* fields. -- Andrew Shadura Thu, 09 May 2013 12:49:04 +0200 tclxml (3.3~svn11-2) unstable; urgency=low * Fix tclconfig to build on GNU/kFreeBSD and GNU/Hurd successfully. * Use dh-autoreconf. -- Andrew O. Shadura Fri, 06 Apr 2012 23:44:44 +0300 tclxml (3.3~svn11-1) unstable; urgency=low * New upstream snapshot. * Update Standards version to 3.9.3. * Move to DebSrc3.0 and dh7. * Split the package into tclxml and tclxml-dev. * Clean up debian/rules. * Add Vcs-* fields. * Include the README file. * Some fixes to the manual pages. * Change the spelling of the maintainer's last name. -- Andrew O. Shadura Thu, 29 Mar 2012 23:09:45 +0200 tclxml (3.2-1) unstable; urgency=low * New maintainer. (Closes: #519315) * New upstream version. (Closes: #540507) * Update Standards version to 3.8.3. -- Andrew O. Shadura Tue, 10 Nov 2009 11:23:08 +0200 tclxml (3.1-3) unstable; urgency=low * Added Readme.html. (Closes: #481810) * Added watch file. * Added Homepage control field. * Update Standards version to 3.8.0. -- Fernando Ike de Oliveira Sun, 29 Jun 2008 23:45:42 -0300 tclxml (3.1-2) unstable; urgency=low * Bug fix: fix directory build package. (Closes: #402791) * Bug fix: fix debian/rules with suggested Kaare Hviid. (Closes: #274192) -- Fernando Ike de Oliveira Thu, 14 Dec 2006 21:59:05 -0200 tclxml (3.1-1) unstable; urgency=low * New upstream release. * New maintainer. * debian/control: - Added expat to Build-Depends. - Added tcllib to Build-Depends. * Updated Standart-Version 3.7.2. * debian/rules: - Remove entried expat. -- Fernando Ike de Oliveira Sun, 30 Jul 2006 12:13:59 -0300 tclxml (3.0-5.1) unstable; urgency=low * Non-maintainer upload during Bug-Squashing-Party. * Added --with-Tclxml=.. to libxml2's configure command line. (Closes: #275734) -- Michael Banck Sun, 28 Nov 2004 00:06:11 +0100 tclxml (3.0-5) unstable; urgency=high * Do 'clean' in libxml2 directory. * Bug fix: "tclxml_3.0-3_sparc: FTBFS: strip: Unable to recognise the format of the input", thanks to Anibal Monsalve Salazar (Closes: #272844). -- David N. Welton Wed, 29 Sep 2004 09:25:32 +0200 tclxml (3.0-4) unstable; urgency=high * Build depend on libxml2-dev. * Bug fix: "tclxml_3.0-3_arm: FTBFS: please use --with-libxml2-include", thanks to Anibal Monsalve Salazar (Closes: #272843). -- David N. Welton Wed, 22 Sep 2004 16:04:09 +0200 tclxml (3.0-3) unstable; urgency=high * Build libxml2 parser too, needed by tcldom. -- David N. Welton Tue, 21 Sep 2004 10:52:27 +0200 tclxml (3.0-2) unstable; urgency=low * Add extra include headers. -- David N. Welton Wed, 1 Sep 2004 11:53:15 +0200 tclxml (3.0-1) unstable; urgency=low * New upstream release -- David N. Welton Wed, 1 Sep 2004 10:59:22 +0200 tclxml (2.6-2) unstable; urgency=low * Bug fix: added tcllib dependancy. Thanks to Sam Hartman (Closes: #216926). -- David N. Welton Tue, 21 Oct 2003 20:57:35 +0200 tclxml (2.6-1) unstable; urgency=low * New upstream release. -- David N. Welton Fri, 14 Mar 2003 17:46:34 -0800 tclxml (2.5-1) unstable; urgency=low * Initial Release. -- David N. Welton Wed, 18 Dec 2002 12:16:22 -0800 debian/source/0000755000000000000000000000000011574737366010511 5ustar debian/source/options0000644000000000000000000000002211574737366012121 0ustar diff-ignore = .hg debian/source/format0000644000000000000000000000001411550651605011700 0ustar 3.0 (quilt) debian/tclxml-dev.install0000644000000000000000000000005211550651605012636 0ustar /usr/include/* /usr/lib/*sh /usr/lib/*/*a