[arch-commits] Commit in xsd/repos (6 files)
Antonio Rojas
arojas at archlinux.org
Sun Oct 15 08:41:53 UTC 2017
Date: Sunday, October 15, 2017 @ 08:41:52
Author: arojas
Revision: 307939
archrelease: copy trunk to staging-i686, staging-x86_64
Added:
xsd/repos/staging-i686/
xsd/repos/staging-i686/PKGBUILD
(from rev 307938, xsd/trunk/PKGBUILD)
xsd/repos/staging-i686/xsdcxx.patch
(from rev 307938, xsd/trunk/xsdcxx.patch)
xsd/repos/staging-x86_64/
xsd/repos/staging-x86_64/PKGBUILD
(from rev 307938, xsd/trunk/PKGBUILD)
xsd/repos/staging-x86_64/xsdcxx.patch
(from rev 307938, xsd/trunk/xsdcxx.patch)
-----------------------------+
staging-i686/PKGBUILD | 36 ++++++++++++
staging-i686/xsdcxx.patch | 126 ++++++++++++++++++++++++++++++++++++++++++
staging-x86_64/PKGBUILD | 36 ++++++++++++
staging-x86_64/xsdcxx.patch | 126 ++++++++++++++++++++++++++++++++++++++++++
4 files changed, 324 insertions(+)
Copied: xsd/repos/staging-i686/PKGBUILD (from rev 307938, xsd/trunk/PKGBUILD)
===================================================================
--- staging-i686/PKGBUILD (rev 0)
+++ staging-i686/PKGBUILD 2017-10-15 08:41:52 UTC (rev 307939)
@@ -0,0 +1,36 @@
+# $Id$
+# Maintainer:
+# Contributor: kevku <kevku at gmx.com>
+
+pkgname=xsd
+pkgver=4.0.0
+_pkgver=4.0.0+dep
+pkgrel=3
+pkgdesc="An open-source, cross-platform W3C XML Schema to C++ data binding compiler"
+arch=('i686' 'x86_64')
+url="http://www.codesynthesis.com/products/xsd"
+license=('GPL2')
+depends=('xerces-c')
+source=("http://www.codesynthesis.com/download/${pkgname}/4.0/${pkgname}-${_pkgver}.tar.bz2"
+ "xsdcxx.patch")
+sha256sums=('eca52a9c8f52cdbe2ae4e364e4a909503493a0d51ea388fc6c9734565a859817'
+ '93f2e6a9dc942cf1fcab7edbe9c38fc102cbaf86f8b667b70aad4e8e2d1e2fd3')
+
+prepare() {
+ cd ${pkgname}-${_pkgver}
+ patch -p1 -i "${srcdir}/xsdcxx.patch"
+}
+
+build() {
+ cd ${pkgname}-${_pkgver}
+ make CXXFLAGS="${CXXFLAGS}"
+}
+
+package() {
+ cd ${pkgname}-${_pkgver}
+ make install_prefix="${pkgdir}/usr" install
+
+ # Fix conflicts with mono
+ mv "${pkgdir}"/usr/bin/xsd{,cxx}
+ mv "${pkgdir}"/usr/share/man/man1/xsd{,cxx}.1
+}
Copied: xsd/repos/staging-i686/xsdcxx.patch (from rev 307938, xsd/trunk/xsdcxx.patch)
===================================================================
--- staging-i686/xsdcxx.patch (rev 0)
+++ staging-i686/xsdcxx.patch 2017-10-15 08:41:52 UTC (rev 307939)
@@ -0,0 +1,126 @@
+--- xsd-4.0.0+dep/xsd/doc/xsd.1~ 2014-09-14 12:25:36.862267587 +0000
++++ xsd-4.0.0+dep/xsd/doc/xsd.1 2014-09-14 12:28:25.728229892 +0000
+@@ -1,16 +1,16 @@
+ .\" Process this file with
+-.\" groff -man -Tascii xsd.1
++.\" groff -man -Tascii xsdcxx.1
+ .\"
+ .TH XSD 1 "July 2014" "XSD 4.0.0"
+ .SH NAME
+-xsd \- W3C XML Schema to C++ Compiler
++xsdcxx \- W3C XML Schema to C++ Compiler
+ .\"
+ .\"
+ .\"
+ .\"--------------------------------------------------------------------
+ .SH SYNOPSIS
+ .\"--------------------------------------------------------------------
+-.B xsd
++.B xsdcxx
+ .I command
+ .B [
+ .I options
+@@ -20,19 +20,19 @@
+ .I file
+ .B ...]
+ .in
+-.B xsd help
++.B xsdcxx help
+ .B [
+ .I command
+ .B ]
+ .in
+-.B xsd version
++.B xsdcxx version
+ .\"
+ .\"
+ .\"
+ .\"--------------------------------------------------------------------
+ .SH DESCRIPTION
+ .\"--------------------------------------------------------------------
+-.B xsd
++.B xsdcxx
+ generates vocabulary-specific, statically-typed C++ mapping from W3C XML
+ Schema definitions. Particular mapping to produce is selected by a
+ .IR command .
+@@ -96,7 +96,7 @@
+ .PP
+ .RS
+ .RS 3
+-.B xsd help
++.B xsdcxx help
+ .I command
+ .RE
+ .PP
+@@ -206,7 +206,7 @@
+ \fIfilename\fP \fInamespace\fP
+
+ For example, if you have file \fBhello\.xsd\fP with namespace
+-\fBhttp://example\.com/hello\fP and you run \fBxsd\fP on this file, then the
++\fBhttp://example\.com/hello\fP and you run \fBxsdcxx\fP on this file, then the
+ string in question will be:
+
+ \fBhello\.xsd\. http://example\.com/hello\fP
+@@ -1632,7 +1632,7 @@
+ .\"
+ .SH DIAGNOSTICS
+ If the input file is not a valid W3C XML Schema definition,
+-.B xsd
++.B xsdcxx
+ will issue diagnostic messages to
+ .B STDERR
+ and exit with non-zero exit code.
+--- xsd-4.0.0+dep/xsd/doc/xsd.xhtml~ 2014-09-14 12:28:37.731513138 +0000
++++ xsd-4.0.0+dep/xsd/doc/xsd.xhtml 2014-09-14 12:30:11.277789610 +0000
+@@ -50,19 +50,19 @@
+
+ <h1>NAME</h1>
+
+- <p>xsd - W3C XML Schema to C++ Compiler</p>
++ <p>xsdcxx - W3C XML Schema to C++ Compiler</p>
+
+ <h1>SYNOPSIS</h1>
+
+ <dl id="synopsis">
+- <dt><code><b>xsd</b> <i>command</i> [<i>options</i>] <i>file</i> [<i>file</i> ...]</code></dt>
+- <dt><code><b>xsd help</b> [<i>command</i>]</code></dt>
+- <dt><code><b>xsd version</b></code></dt>
++ <dt><code><b>xsdcxx</b> <i>command</i> [<i>options</i>] <i>file</i> [<i>file</i> ...]</code></dt>
++ <dt><code><b>xsdcxx help</b> [<i>command</i>]</code></dt>
++ <dt><code><b>xsdcxx version</b></code></dt>
+ </dl>
+
+ <h1>DESCRIPTION</h1>
+
+- <p><code><b>xsd</b></code> generates vocabulary-specific, statically-typed
++ <p><code><b>xsdcxx</b></code> generates vocabulary-specific, statically-typed
+ C++ mapping from W3C XML Schema definitions. Particular mapping to
+ produce is selected by a <code><i>command</i></code>. Each mapping has
+ a number of mapping-specific <code><i>options</i></code> that should
+@@ -104,7 +104,7 @@
+
+ <dt><code><b>help</b></code></dt>
+ <dd>Print usage information and exit. Use
+- <p><code><b>xsd help</b> <i>command</i></code></p>
++ <p><code><b>xsdcxx help</b> <i>command</i></code></p>
+ for command-specific help.
+ </dd>
+
+@@ -219,7 +219,7 @@
+
+ <p>For example, if you have file <code><b>hello.xsd</b></code> with
+ namespace <code><b>http://example.com/hello</b></code> and you run
+- <code><b>xsd</b></code> on this file, then the string in question will
++ <code><b>xsdcxx</b></code> on this file, then the string in question will
+ be:</p>
+
+ <p><code><b>hello.xsd. http://example.com/hello</b></code></p>
+@@ -1530,7 +1530,7 @@
+ <h1>DIAGNOSTICS</h1>
+
+ <p>If the input file is not a valid W3C XML Schema definition,
+- <code><b>xsd</b></code> will issue diagnostic messages to STDERR
++ <code><b>xsdcxx</b></code> will issue diagnostic messages to STDERR
+ and exit with non-zero exit code.</p>
+
+ <h1>BUGS</h1>
Copied: xsd/repos/staging-x86_64/PKGBUILD (from rev 307938, xsd/trunk/PKGBUILD)
===================================================================
--- staging-x86_64/PKGBUILD (rev 0)
+++ staging-x86_64/PKGBUILD 2017-10-15 08:41:52 UTC (rev 307939)
@@ -0,0 +1,36 @@
+# $Id$
+# Maintainer:
+# Contributor: kevku <kevku at gmx.com>
+
+pkgname=xsd
+pkgver=4.0.0
+_pkgver=4.0.0+dep
+pkgrel=3
+pkgdesc="An open-source, cross-platform W3C XML Schema to C++ data binding compiler"
+arch=('i686' 'x86_64')
+url="http://www.codesynthesis.com/products/xsd"
+license=('GPL2')
+depends=('xerces-c')
+source=("http://www.codesynthesis.com/download/${pkgname}/4.0/${pkgname}-${_pkgver}.tar.bz2"
+ "xsdcxx.patch")
+sha256sums=('eca52a9c8f52cdbe2ae4e364e4a909503493a0d51ea388fc6c9734565a859817'
+ '93f2e6a9dc942cf1fcab7edbe9c38fc102cbaf86f8b667b70aad4e8e2d1e2fd3')
+
+prepare() {
+ cd ${pkgname}-${_pkgver}
+ patch -p1 -i "${srcdir}/xsdcxx.patch"
+}
+
+build() {
+ cd ${pkgname}-${_pkgver}
+ make CXXFLAGS="${CXXFLAGS}"
+}
+
+package() {
+ cd ${pkgname}-${_pkgver}
+ make install_prefix="${pkgdir}/usr" install
+
+ # Fix conflicts with mono
+ mv "${pkgdir}"/usr/bin/xsd{,cxx}
+ mv "${pkgdir}"/usr/share/man/man1/xsd{,cxx}.1
+}
Copied: xsd/repos/staging-x86_64/xsdcxx.patch (from rev 307938, xsd/trunk/xsdcxx.patch)
===================================================================
--- staging-x86_64/xsdcxx.patch (rev 0)
+++ staging-x86_64/xsdcxx.patch 2017-10-15 08:41:52 UTC (rev 307939)
@@ -0,0 +1,126 @@
+--- xsd-4.0.0+dep/xsd/doc/xsd.1~ 2014-09-14 12:25:36.862267587 +0000
++++ xsd-4.0.0+dep/xsd/doc/xsd.1 2014-09-14 12:28:25.728229892 +0000
+@@ -1,16 +1,16 @@
+ .\" Process this file with
+-.\" groff -man -Tascii xsd.1
++.\" groff -man -Tascii xsdcxx.1
+ .\"
+ .TH XSD 1 "July 2014" "XSD 4.0.0"
+ .SH NAME
+-xsd \- W3C XML Schema to C++ Compiler
++xsdcxx \- W3C XML Schema to C++ Compiler
+ .\"
+ .\"
+ .\"
+ .\"--------------------------------------------------------------------
+ .SH SYNOPSIS
+ .\"--------------------------------------------------------------------
+-.B xsd
++.B xsdcxx
+ .I command
+ .B [
+ .I options
+@@ -20,19 +20,19 @@
+ .I file
+ .B ...]
+ .in
+-.B xsd help
++.B xsdcxx help
+ .B [
+ .I command
+ .B ]
+ .in
+-.B xsd version
++.B xsdcxx version
+ .\"
+ .\"
+ .\"
+ .\"--------------------------------------------------------------------
+ .SH DESCRIPTION
+ .\"--------------------------------------------------------------------
+-.B xsd
++.B xsdcxx
+ generates vocabulary-specific, statically-typed C++ mapping from W3C XML
+ Schema definitions. Particular mapping to produce is selected by a
+ .IR command .
+@@ -96,7 +96,7 @@
+ .PP
+ .RS
+ .RS 3
+-.B xsd help
++.B xsdcxx help
+ .I command
+ .RE
+ .PP
+@@ -206,7 +206,7 @@
+ \fIfilename\fP \fInamespace\fP
+
+ For example, if you have file \fBhello\.xsd\fP with namespace
+-\fBhttp://example\.com/hello\fP and you run \fBxsd\fP on this file, then the
++\fBhttp://example\.com/hello\fP and you run \fBxsdcxx\fP on this file, then the
+ string in question will be:
+
+ \fBhello\.xsd\. http://example\.com/hello\fP
+@@ -1632,7 +1632,7 @@
+ .\"
+ .SH DIAGNOSTICS
+ If the input file is not a valid W3C XML Schema definition,
+-.B xsd
++.B xsdcxx
+ will issue diagnostic messages to
+ .B STDERR
+ and exit with non-zero exit code.
+--- xsd-4.0.0+dep/xsd/doc/xsd.xhtml~ 2014-09-14 12:28:37.731513138 +0000
++++ xsd-4.0.0+dep/xsd/doc/xsd.xhtml 2014-09-14 12:30:11.277789610 +0000
+@@ -50,19 +50,19 @@
+
+ <h1>NAME</h1>
+
+- <p>xsd - W3C XML Schema to C++ Compiler</p>
++ <p>xsdcxx - W3C XML Schema to C++ Compiler</p>
+
+ <h1>SYNOPSIS</h1>
+
+ <dl id="synopsis">
+- <dt><code><b>xsd</b> <i>command</i> [<i>options</i>] <i>file</i> [<i>file</i> ...]</code></dt>
+- <dt><code><b>xsd help</b> [<i>command</i>]</code></dt>
+- <dt><code><b>xsd version</b></code></dt>
++ <dt><code><b>xsdcxx</b> <i>command</i> [<i>options</i>] <i>file</i> [<i>file</i> ...]</code></dt>
++ <dt><code><b>xsdcxx help</b> [<i>command</i>]</code></dt>
++ <dt><code><b>xsdcxx version</b></code></dt>
+ </dl>
+
+ <h1>DESCRIPTION</h1>
+
+- <p><code><b>xsd</b></code> generates vocabulary-specific, statically-typed
++ <p><code><b>xsdcxx</b></code> generates vocabulary-specific, statically-typed
+ C++ mapping from W3C XML Schema definitions. Particular mapping to
+ produce is selected by a <code><i>command</i></code>. Each mapping has
+ a number of mapping-specific <code><i>options</i></code> that should
+@@ -104,7 +104,7 @@
+
+ <dt><code><b>help</b></code></dt>
+ <dd>Print usage information and exit. Use
+- <p><code><b>xsd help</b> <i>command</i></code></p>
++ <p><code><b>xsdcxx help</b> <i>command</i></code></p>
+ for command-specific help.
+ </dd>
+
+@@ -219,7 +219,7 @@
+
+ <p>For example, if you have file <code><b>hello.xsd</b></code> with
+ namespace <code><b>http://example.com/hello</b></code> and you run
+- <code><b>xsd</b></code> on this file, then the string in question will
++ <code><b>xsdcxx</b></code> on this file, then the string in question will
+ be:</p>
+
+ <p><code><b>hello.xsd. http://example.com/hello</b></code></p>
+@@ -1530,7 +1530,7 @@
+ <h1>DIAGNOSTICS</h1>
+
+ <p>If the input file is not a valid W3C XML Schema definition,
+- <code><b>xsd</b></code> will issue diagnostic messages to STDERR
++ <code><b>xsdcxx</b></code> will issue diagnostic messages to STDERR
+ and exit with non-zero exit code.</p>
+
+ <h1>BUGS</h1>
More information about the arch-commits
mailing list