github-markup 3.0.2 → 3.0.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 4a1ac869e4b4e23a417481b72789919fcfd5f7681a7109d13b58436bdf686b3a
-  data.tar.gz: b3e9e1e23c8f3253fc1c169a76839b06ded3f121442c063acb7a0c9704772631
+  metadata.gz: c3af7e9cf8ed0fbc63c2705e680b36470373ee6c8d65f4140364c850413b9e3c
+  data.tar.gz: 64d493460cd36838258eba6c51b8fb6d8273780aa9a4de4ccd70567016d44ec3
 SHA512:
-  metadata.gz: 13f584545ee0d79316a3f68d080b3f0c44a31a1b8e23468ed3b8da611d4933bb6eeb183c29b918484d1218cb132a3dbd77ca87fd4c5bc89bd53738a1c1b04cfa
-  data.tar.gz: 63977e1c80e89c7d976dae9c119b1f28c5c27e3066f8cd610d31e9ef3a61d3531fffd323b729c16446eb8abf3ec19d92bb321e0fa5a5503b1a8198461031a8b8
+  metadata.gz: b02b26218266f9fdbf1211ee4cea875936936ddebed1a4b784b327a2911c1ae8ba6173f98b3d78b06b8e558afb87f707c136eac00a1e7696d6b0d610c4864bed
+  data.tar.gz: 29820c650182ee9fb73cfbbe809a89ae7aa681359b8cd3d5116bc7cfe59e72cf96f971cdb96bc67d26e42546bc4b56d1694f31f735eeb465897db6d242491889

data/.travis.yml

@@ -6,9 +6,6 @@ rvm:
   - 2.2.7
   - 2.3.4
   - 2.4.1
-  - jruby-9.1.9.0
-jdk:
-  - oraclejdk8
 notifications:
   email: false
 git:
@@ -18,7 +15,7 @@ before_install:
   - echo "deb https://dl.bintray.com/nxadm/rakudo-pkg-debs `lsb_release -cs` main" | sudo tee -a /etc/apt/sources.list.d/rakudo-pkg.list
   - sudo apt-get update -qq
   - sudo apt-get install perl rakudo-pkg
-  - export PATH=$PATH:/.perl6/bin:/opt/rakudo-pkg/bin && install-zef-as-user && zef install Pod::To::HTML
+  - export PATH=$PATH:/.perl6/bin:/opt/rakudo-pkg/bin
   - curl -L http://cpanmin.us | perl - --sudo App::cpanminus
   - sudo cpanm --installdeps --notest Pod::Simple
   - sudo pip install docutils
@@ -28,6 +25,3 @@ cache:
 env:
   global:
     - "JRUBY_OPTS=-Xcext.enabled=true"
-matrix:
- allow_failures:
-   - rvm: jruby-9.1.9.0

data/HISTORY.md

@@ -1,3 +1,7 @@
+## 3.0.3 - 2018-12-17
+
+* Temporarily remove support for POD6 [#1248](https://github.com/github/markup/pull/1248)
+
 ## 3.0.2 - 2018-12-12
 
 * Add support for POD6 [#1173](https://github.com/github/markup/pull/1173)

data/github-markup.gemspec

@@ -12,7 +12,7 @@ Gem::Specification.new do |s|
   s.license       = "MIT"
 
   s.files         = `git ls-files`.split($\)
-  s.files        += Dir['vendor/Pod-To-HTML/**/*']
+  s.files        += Dir['vendor/**/*']
   s.executables   = s.files.grep(%r{^bin/}).map{ |f| File.basename(f) }
   s.test_files    = s.files.grep(%r{^(test|spec|features)/})
   s.require_paths = %w[lib]

data/lib/github-markup.rb

@@ -1,6 +1,6 @@
 module GitHub
   module Markup
-    VERSION = '3.0.2'
+    VERSION = '3.0.3'
     Version = VERSION
   end
 end

data/lib/github/commands/pod62html

@@ -1,10 +1,5 @@
 #!/usr/bin/env perl6
 
 use v6;
-use lib $*PROGRAM.IO.parent.add: '../../../vendor/Pod-To-HTML';
-use Pod::To::HTML;
 
-$_ = Pod::To::HTML.render(slurp);
-s:s{\<\!doctype html\>.*\<div id\=\"___top\"\>\<\/div\>\s*} = "";
-s:s{\s*\<\/div\>\s*\<\/body\>\s*\<\/html\>\s*} = "";
-.put;
+slurp.put;

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: github-markup
 version: !ruby/object:Gem::Version
-  version: 3.0.2
+  version: 3.0.3
 platform: ruby
 authors:
 - Chris Wanstrath
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2018-12-12 00:00:00.000000000 Z
+date: 2018-12-17 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rake
@@ -144,7 +144,6 @@ extra_rdoc_files: []
 files:
 - ".dockerignore"
 - ".gitignore"
-- ".gitmodules"
 - ".kick"
 - ".travis.yml"
 - CODE_OF_CONDUCT.md
@@ -191,8 +190,6 @@ files:
 - test/markups/README.org.html
 - test/markups/README.pod
 - test/markups/README.pod.html
-- test/markups/README.pod6
-- test/markups/README.pod6.html
 - test/markups/README.rdoc
 - test/markups/README.rdoc.html
 - test/markups/README.rst
@@ -205,31 +202,6 @@ files:
 - test/markups/README.toc.rst.html
 - test/markups/README.txt
 - test/markups/README.txt.html
-- vendor/Pod-To-HTML/LICENSE
-- vendor/Pod-To-HTML/META6.json
-- vendor/Pod-To-HTML/README.md
-- vendor/Pod-To-HTML/README.pod6
-- vendor/Pod-To-HTML/TODO
-- vendor/Pod-To-HTML/lib/Pod/To/HTML.pm
-- vendor/Pod-To-HTML/resources/examples/01-parse-files.p6
-- vendor/Pod-To-HTML/resources/examples/README.md
-- vendor/Pod-To-HTML/resources/examples/main.mustache
-- vendor/Pod-To-HTML/resources/examples/render.p6
-- vendor/Pod-To-HTML/resources/templates/main.mustache
-- vendor/Pod-To-HTML/t/010-basic.t
-- vendor/Pod-To-HTML/t/020-code.t
-- vendor/Pod-To-HTML/t/030-comment.t
-- vendor/Pod-To-HTML/t/040-lists.t
-- vendor/Pod-To-HTML/t/050-format-x-index.t
-- vendor/Pod-To-HTML/t/060-table.t
-- vendor/Pod-To-HTML/t/070-headings.t
-- vendor/Pod-To-HTML/t/075-defn.t
-- vendor/Pod-To-HTML/t/080-lang.t
-- vendor/Pod-To-HTML/t/090-css.t
-- vendor/Pod-To-HTML/t/100-issue-37.t
-- vendor/Pod-To-HTML/t/110-issue-41.t
-- vendor/Pod-To-HTML/t/120-templates.t
-- vendor/Pod-To-HTML/t/templates/main.mustache
 homepage: https://github.com/github/markup
 licenses:
 - MIT
@@ -275,8 +247,6 @@ test_files:
 - test/markups/README.org.html
 - test/markups/README.pod
 - test/markups/README.pod.html
-- test/markups/README.pod6
-- test/markups/README.pod6.html
 - test/markups/README.rdoc
 - test/markups/README.rdoc.html
 - test/markups/README.rst

data/.gitmodules

@@ -1,3 +0,0 @@
-[submodule "vendor/Pod-To-HTML"]
-	path = vendor/Pod-To-HTML
-	url = https://github.com/perl6/Pod-To-HTML

data/test/markups/README.pod6

@@ -1,151 +0,0 @@
-=begin pod 
-
-=TITLE About the Docs
-
-=SUBTITLE Meta-documentation
-
-This document collection represents the on-going effort to document the Perl 6 programming
-language with the goals of being: comprehensive; easy to use; easy to
-navigate; and useful to both newcomers and experienced Perl 6
-programmers.
-
-An HTML version of the documentation is located online at
-L<https://docs.perl6.org>.
-
-The official source for this documentation is located at L<perl6/doc on
-GitHub|https://github.com/perl6/doc>.
-
-This particular document is a quick overview of the process
-described in more detail in L<CONTRIBUTING on GitHub|https://github.com/perl6/doc/blob/master/CONTRIBUTING.md>.
-This document also provides a short introduction to writing Perl 6
-Pod files, which can be rendered into HTML and other formats.
-
-=head1 Structure
-
-All of the documentation is written in Perl 6 Pod and kept in the C<doc/>
-directory, and the C<doc/Language/> and C<doc/Type/> sub-directories.
-These files are processed as collections of definitions or
-"documentables", which are then post-processed and linked together.
-
-=head1 Generating HTML from Pod
-
-To generate HTML from the Pod files, you'll need:
-
-=item A recent version of the Rakudo Perl 6 compiler
-
-=item The Perl 6 modules Pod::To::HTML, Pod::To::BigPage, and URI::Escape
-(can be installed via L<zef|https://github.com/ugexe/zef>).
-
-=item B<Optional>: L<GraphViz|http://graphviz.org>, for creating graphs
-of the relationships between Perl 6 types
-
-=item B<Optional>: L<Atom Highlights|https://github.com/atom/highlights> and L<language-perl6|https://atom.io/packages/language-perl6>, for syntax
-highlighting
-
-To generate the documentation into the C<html/> folder, run:
-
-=begin code :lang<shell>
-perl6 htmlify.p6
-=end code
-
-To host the documentation from a web server, have Perl 5
-and Mojolicious::Lite installed, then run:
-
-=begin code :lang<shell>
-perl app.pl daemon
-=end code
-
-=head1 Contributing
-
-The documentation is written in Perl 6 Pod.
-
-For a quick introduction to Perl 6 Pod, see L<Perl 6 Pod|https://docs.perl6.org/language/pod>.
-
-For full details about the Perl 6 Pod specification, see L<Synopsis 26, Documentation|https://design.perl6.org/S26.html>.
-
-=head2 Adding definitions
-
-Documentables can be defined using an C<=headN> Pod directive, where
-C<N> is greater than zero (e.g., C<=head1>, C<=head2>, …).
-
-All of the paragraphs and blocks following that directive, up until the
-next directive of the same level, will be considered part of the
-documentable. So, in:
-
-=begin code :allow<R> :skip-test
-=head2 R<My Definition>
-
-Some paragraphs, followed by some code:
-
-    my Code $examples = "amazing";
-
-Mind === blown.
-
-=head3 Minor details about R<My Definition>
-
-It's fantastic.
-
-=head2 And now, for something completely different
-
-…
-
-=end code
-
-The documentable R<My Definition> extends down to the C<=head2 And now…>.
-
-Documentables may contain other documentables. Class documentables, for
-example, often contain the methods the class implements.
-
-Definitions must be in one of the following forms to be recognized as
-the start of a documentable named, say, þ.  First the code in the document source:
-
-=begin code :skip-test
-
-=item X<C<How to use the þ infix> | infix,þ> (This a special case, which
-is always considered a definition)
-
-=item C<The þ Infix>
-
-=item B<The C<þ> Infix>
-
-=item C<Infix þ>
-
-=item B<Infix C<þ>>
-
-=item C<trait is cached> (A special case for the L<trait|/language/functions#Traits> documentables)
-
-=end code
-
-Then the results on the rendered page:
-
-=item X<C<How to use the þ infix> | infix,þ> (This is a special case, which
-is always considered a definition)
-
-=item C<The þ Infix>
-
-=item B<The C<þ> Infix>
-
-=item C<Infix þ>
-
-=item B<Infix C<þ>>
-
-=item C<trait is cached> (A special case for the L<trait|/language/functions#Traits> documentables)
-
-These items should now be searchable by using the search field in the HTML docs.
-
-You can add emphasis with bold (B<V< B<> >>) or italicized (B<V< I<> >>),
-with or without code formatting (B<V< C<> >>).  Due to current parser limitations,
-special steps have to be taken to use B<V< X<> >> with other formatting codes; for example:
-
-=begin code :skip-test
-=item X<B<foo>|foo> a fancy subroutine
-=end code
-
-renders like this
-
-=item X<B<foo>|foo> a fancy subroutine
-
-Notice that text after a pipe ('|') has no formatting. Also note that B<V< C<> >>
-preserves spaces and treats text as verbatim.
-=end pod
-

data/test/markups/README.pod6.html

@@ -1,128 +0,0 @@
-<h1>About the Docs</h1>
-    <p>Meta-documentation</p>
-     
-<table>
-<h2>Table of Contents</h2>
-            <tr>
-<td>1</td>
-<td><a href="#Structure">Structure</a></td>
-</tr>
-        <tr>
-<td>2</td>
-<td><a href="#Generating_HTML_from_Pod">Generating HTML from Pod</a></td>
-</tr>
-                        <tr>
-<td>3</td>
-<td><a href="#Contributing">Contributing</a></td>
-</tr>
-        <tr>
-<td>3.1</td>
-<td><a href="#Adding_definitions">Adding definitions</a></td>
-</tr>
-                                                                                               
-</table>
- 
-
-    <div>
-    <p>This document collection represents the on-going effort to document the Perl 6 programming language with the goals of being: comprehensive; easy to use; easy to navigate; and useful to both newcomers and experienced Perl 6 programmers.</p>
-<p>An HTML version of the documentation is located online at <a href="https://docs.perl6.org">https://docs.perl6.org</a>.</p>
-<p>The official source for this documentation is located at <a href="https://github.com/perl6/doc">perl6/doc on GitHub</a>.</p>
-<p>This particular document is a quick overview of the process described in more detail in <a href="https://github.com/perl6/doc/blob/master/CONTRIBUTING.md">CONTRIBUTING on GitHub</a>. This document also provides a short introduction to writing Perl 6 Pod files, which can be rendered into HTML and other formats.</p>
-<h1><a href="#___top" title="go to top of document">Structure</a></h1>
-<p>All of the documentation is written in Perl 6 Pod and kept in the <code>doc/</code> directory, and the <code>doc/Language/</code> and <code>doc/Type/</code> sub-directories. These files are processed as collections of definitions or "documentables", which are then post-processed and linked together.</p>
-<h1><a href="#___top" title="go to top of document">Generating HTML from Pod</a></h1>
-<p>To generate HTML from the Pod files, you'll need:</p>
-<ul>
-<li>
-<p>A recent version of the Rakudo Perl 6 compiler</p>
-</li>
-<li>
-<p>The Perl 6 modules Pod::To::HTML, Pod::To::BigPage, and URI::Escape (can be installed via <a href="https://github.com/ugexe/zef">zef</a>).</p>
-</li>
-<li>
-<p><strong>Optional</strong>: <a href="http://graphviz.org">GraphViz</a>, for creating graphs of the relationships between Perl 6 types</p>
-</li>
-<li>
-<p><strong>Optional</strong>: <a href="https://github.com/atom/highlights">Atom Highlights</a> and <a href="https://atom.io/packages/language-perl6">language-perl6</a>, for syntax highlighting</p>
-</li>
-</ul>
-<p>To generate the documentation into the <code>html/</code> folder, run:</p>
-<pre>perl6 htmlify.p6
-</pre>
-<p>To host the documentation from a web server, have Perl 5 and Mojolicious::Lite installed, then run:</p>
-<pre>perl app.pl daemon
-</pre>
-<h1><a href="#___top" title="go to top of document">Contributing</a></h1>
-<p>The documentation is written in Perl 6 Pod.</p>
-<p>For a quick introduction to Perl 6 Pod, see <a href="https://docs.perl6.org/language/pod">Perl 6 Pod</a>.</p>
-<p>For full details about the Perl 6 Pod specification, see <a href="https://design.perl6.org/S26.html">Synopsis 26, Documentation</a>.</p>
-<h2><a href="#___top" title="go to top of document">Adding definitions</a></h2>
-<p>Documentables can be defined using an <code>=headN</code> Pod directive, where <code>N</code> is greater than zero (e.g., <code>=head1</code>, <code>=head2</code>, …).</p>
-<p>All of the paragraphs and blocks following that directive, up until the next directive of the same level, will be considered part of the documentable. So, in:</p>
-<pre>=head2 <var>My Definition</var>
-
-Some paragraphs, followed by some code:
-
-    my Code $examples = "amazing";
-
-Mind === blown.
-
-=head3 Minor details about <var>My Definition</var>
-
-It's fantastic.
-
-=head2 And now, for something completely different
-
-…
-
-</pre>
-<p>The documentable <var>My Definition</var> extends down to the <code>=head2 And now…</code>.</p>
-<p>Documentables may contain other documentables. Class documentables, for example, often contain the methods the class implements.</p>
-<p>Definitions must be in one of the following forms to be recognized as the start of a documentable named, say, þ. First the code in the document source:</p>
-<pre>=item X&lt;C&lt;How to use the þ infix&gt; | infix,þ&gt; (This a special case, which
-is always considered a definition)
-
-=item C&lt;The þ Infix&gt;
-
-=item B&lt;The C&lt;þ&gt; Infix&gt;
-
-=item C&lt;Infix þ&gt;
-
-=item B&lt;Infix C&lt;þ&gt;&gt;
-
-=item C&lt;trait is cached&gt; (A special case for the L&lt;trait|/language/functions#Traits&gt; documentables)
-
-</pre>
-<p>Then the results on the rendered page:</p>
-<ul>
-<li>
-<p><a name="index-entry-infix_%C3%BE-How_to_use_the_%C3%BE_infix"><code>How to use the þ infix</code></a> (This is a special case, which is always considered a definition)</p>
-</li>
-<li>
-<p><code>The þ Infix</code></p>
-</li>
-<li>
-<p><strong>The <code>þ</code> Infix</strong></p>
-</li>
-<li>
-<p><code>Infix þ</code></p>
-</li>
-<li>
-<p><strong>Infix <code>þ</code></strong></p>
-</li>
-<li>
-<p><code>trait is cached</code> (A special case for the <a href="/language/functions#Traits">trait</a> documentables)</p>
-</li>
-</ul>
-<p>These items should now be searchable by using the search field in the HTML docs.</p>
-<p>You can add emphasis with bold (<strong> B&lt;&gt; </strong>) or italicized (<strong> I&lt;&gt; </strong>), with or without code formatting (<strong> C&lt;&gt; </strong>). Due to current parser limitations, special steps have to be taken to use <strong> X&lt;&gt; </strong> with other formatting codes; for example:</p>
-<pre>=item X&lt;B&lt;foo&gt;|foo&gt; a fancy subroutine
-</pre>
-<p>renders like this</p>
-<ul>
-<li>
-<p><a name="index-entry-foo-foo"><strong>foo</strong></a> a fancy subroutine</p>
-</li>
-</ul>
-<p>Notice that text after a pipe ('|') has no formatting. Also note that <strong> C&lt;&gt; </strong> preserves spaces and treats text as verbatim.</p>
-</div>

data/vendor/Pod-To-HTML/LICENSE

@@ -1,201 +0,0 @@
-		       The Artistic License 2.0
-
-	    Copyright (c) 2000-2006, The Perl Foundation.
-
-     Everyone is permitted to copy and distribute verbatim copies
-      of this license document, but changing it is not allowed.
-
-Preamble
-
-This license establishes the terms under which a given free software
-Package may be copied, modified, distributed, and/or redistributed.
-The intent is that the Copyright Holder maintains some artistic
-control over the development of that Package while still keeping the
-Package available as open source and free software.
-
-You are always permitted to make arrangements wholly outside of this
-license directly with the Copyright Holder of a given Package.  If the
-terms of this license do not permit the full use that you propose to
-make of the Package, you should contact the Copyright Holder and seek
-a different licensing arrangement. 
-
-Definitions
-
-    "Copyright Holder" means the individual(s) or organization(s)
-    named in the copyright notice for the entire Package.
-
-    "Contributor" means any party that has contributed code or other
-    material to the Package, in accordance with the Copyright Holder's
-    procedures.
-
-    "You" and "your" means any person who would like to copy,
-    distribute, or modify the Package.
-
-    "Package" means the collection of files distributed by the
-    Copyright Holder, and derivatives of that collection and/or of
-    those files. A given Package may consist of either the Standard
-    Version, or a Modified Version.
-
-    "Distribute" means providing a copy of the Package or making it
-    accessible to anyone else, or in the case of a company or
-    organization, to others outside of your company or organization.
-
-    "Distributor Fee" means any fee that you charge for Distributing
-    this Package or providing support for this Package to another
-    party.  It does not mean licensing fees.
-
-    "Standard Version" refers to the Package if it has not been
-    modified, or has been modified only in ways explicitly requested
-    by the Copyright Holder.
-
-    "Modified Version" means the Package, if it has been changed, and
-    such changes were not explicitly requested by the Copyright
-    Holder. 
-
-    "Original License" means this Artistic License as Distributed with
-    the Standard Version of the Package, in its current version or as
-    it may be modified by The Perl Foundation in the future.
-
-    "Source" form means the source code, documentation source, and
-    configuration files for the Package.
-
-    "Compiled" form means the compiled bytecode, object code, binary,
-    or any other form resulting from mechanical transformation or
-    translation of the Source form.
-
-
-Permission for Use and Modification Without Distribution
-
-(1)  You are permitted to use the Standard Version and create and use
-Modified Versions for any purpose without restriction, provided that
-you do not Distribute the Modified Version.
-
-
-Permissions for Redistribution of the Standard Version
-
-(2)  You may Distribute verbatim copies of the Source form of the
-Standard Version of this Package in any medium without restriction,
-either gratis or for a Distributor Fee, provided that you duplicate
-all of the original copyright notices and associated disclaimers.  At
-your discretion, such verbatim copies may or may not include a
-Compiled form of the Package.
-
-(3)  You may apply any bug fixes, portability changes, and other
-modifications made available from the Copyright Holder.  The resulting
-Package will still be considered the Standard Version, and as such
-will be subject to the Original License.
-
-
-Distribution of Modified Versions of the Package as Source 
-
-(4)  You may Distribute your Modified Version as Source (either gratis
-or for a Distributor Fee, and with or without a Compiled form of the
-Modified Version) provided that you clearly document how it differs
-from the Standard Version, including, but not limited to, documenting
-any non-standard features, executables, or modules, and provided that
-you do at least ONE of the following:
-
-    (a)  make the Modified Version available to the Copyright Holder
-    of the Standard Version, under the Original License, so that the
-    Copyright Holder may include your modifications in the Standard
-    Version.
-
-    (b)  ensure that installation of your Modified Version does not
-    prevent the user installing or running the Standard Version. In
-    addition, the Modified Version must bear a name that is different
-    from the name of the Standard Version.
-
-    (c)  allow anyone who receives a copy of the Modified Version to
-    make the Source form of the Modified Version available to others
-    under
-		
-	(i)  the Original License or
-
-	(ii)  a license that permits the licensee to freely copy,
-	modify and redistribute the Modified Version using the same
-	licensing terms that apply to the copy that the licensee
-	received, and requires that the Source form of the Modified
-	Version, and of any works derived from it, be made freely
-	available in that license fees are prohibited but Distributor
-	Fees are allowed.
-
-
-Distribution of Compiled Forms of the Standard Version 
-or Modified Versions without the Source
-
-(5)  You may Distribute Compiled forms of the Standard Version without
-the Source, provided that you include complete instructions on how to
-get the Source of the Standard Version.  Such instructions must be
-valid at the time of your distribution.  If these instructions, at any
-time while you are carrying out such distribution, become invalid, you
-must provide new instructions on demand or cease further distribution.
-If you provide valid instructions or cease distribution within thirty
-days after you become aware that the instructions are invalid, then
-you do not forfeit any of your rights under this license.
-
-(6)  You may Distribute a Modified Version in Compiled form without
-the Source, provided that you comply with Section 4 with respect to
-the Source of the Modified Version.
-
-
-Aggregating or Linking the Package 
-
-(7)  You may aggregate the Package (either the Standard Version or
-Modified Version) with other packages and Distribute the resulting
-aggregation provided that you do not charge a licensing fee for the
-Package.  Distributor Fees are permitted, and licensing fees for other
-components in the aggregation are permitted. The terms of this license
-apply to the use and Distribution of the Standard or Modified Versions
-as included in the aggregation.
-
-(8) You are permitted to link Modified and Standard Versions with
-other works, to embed the Package in a larger work of your own, or to
-build stand-alone binary or bytecode versions of applications that
-include the Package, and Distribute the result without restriction,
-provided the result does not expose a direct interface to the Package.
-
-
-Items That are Not Considered Part of a Modified Version 
-
-(9) Works (including, but not limited to, modules and scripts) that
-merely extend or make use of the Package, do not, by themselves, cause
-the Package to be a Modified Version.  In addition, such works are not
-considered parts of the Package itself, and are not subject to the
-terms of this license.
-
-
-General Provisions
-
-(10)  Any use, modification, and distribution of the Standard or
-Modified Versions is governed by this Artistic License. By using,
-modifying or distributing the Package, you accept this license. Do not
-use, modify, or distribute the Package, if you do not accept this
-license.
-
-(11)  If your Modified Version has been derived from a Modified
-Version made by someone other than you, you are nevertheless required
-to ensure that your Modified Version complies with the requirements of
-this license.
-
-(12)  This license does not grant you the right to use any trademark,
-service mark, tradename, or logo of the Copyright Holder.
-
-(13)  This license includes the non-exclusive, worldwide,
-free-of-charge patent license to make, have made, use, offer to sell,
-sell, import and otherwise transfer the Package with respect to any
-patent claims licensable by the Copyright Holder that are necessarily
-infringed by the Package. If you institute patent litigation
-(including a cross-claim or counterclaim) against any party alleging
-that the Package constitutes direct or contributory patent
-infringement, then this Artistic License to you shall terminate on the
-date that such litigation is filed.
-
-(14)  Disclaimer of Warranty:
-THE PACKAGE IS PROVIDED BY THE COPYRIGHT HOLDER AND CONTRIBUTORS "AS
-IS" AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES. THE IMPLIED
-WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR
-NON-INFRINGEMENT ARE DISCLAIMED TO THE EXTENT PERMITTED BY YOUR LOCAL
-LAW. UNLESS REQUIRED BY LAW, NO COPYRIGHT HOLDER OR CONTRIBUTOR WILL
-BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
-DAMAGES ARISING IN ANY WAY OUT OF THE USE OF THE PACKAGE, EVEN IF
-ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.