From 511398b8de4d3cedf8e7404617174c7e248630d5 Mon Sep 17 00:00:00 2001
From: lili <me@miquellionel.ovh>
Date: Tue, 2 Apr 2019 13:13:05 +0200
Subject: nuspec added

---
 xidel.nuspec | 116 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 116 insertions(+)
 create mode 100644 xidel.nuspec

diff --git a/xidel.nuspec b/xidel.nuspec
new file mode 100644
index 0000000..e0aaa9c
--- /dev/null
+++ b/xidel.nuspec
@@ -0,0 +1,116 @@
+<?xml version="1.0" encoding="utf-8"?>
+ 
+<!-- Read this before creating packages: https://chocolatey.org/docs/create-packages -->
+<!-- It is especially important to read the above link to understand additional requirements when publishing packages to the community feed aka dot org (https://chocolatey.org/packages). -->
+
+<!-- Test your packages in a test environment: https://github.com/chocolatey/chocolatey-test-environment -->
+
+<!--
+This is a nuspec. It mostly adheres to https://docs.nuget.org/create/Nuspec-Reference. Chocolatey uses a special version of NuGet.Core that allows us to do more than was initially possible. As such there are certain things to be aware of:
+
+* the package xmlns schema url may cause issues with nuget.exe
+* Any of the following elements can ONLY be used by choco tools - projectSourceUrl, docsUrl, mailingListUrl, bugTrackerUrl, packageSourceUrl, provides, conflicts, replaces 
+* nuget.exe can still install packages with those elements but they are ignored. Any authoring tools or commands will error on those elements 
+-->
+
+<!-- You can embed software files directly into packages, as long as you are not bound by distribution rights. -->
+<!-- * If you are an organization making private packages, you probably have no issues here -->
+<!-- * If you are releasing to the community feed, you need to consider distribution rights. -->
+<!-- Do not remove this test for UTF-8: if “Ω” doesn’t appear as greek uppercase omega letter enclosed in quotation marks, you should use an editor that supports UTF-8, not this one. -->
+<package xmlns="http://schemas.microsoft.com/packaging/2015/06/nuspec.xsd">
+  <metadata>
+    <!-- == PACKAGE SPECIFIC SECTION == -->
+    <!-- This section is about this package, although id and version have ties back to the software -->
+    <!-- id is lowercase and if you want a good separator for words, use '-', not '.'. Dots are only acceptable as suffixes for certain types of packages, e.g. .install, .portable, .extension, .template -->
+    <!-- If the software is cross-platform, attempt to use the same id as the debian/rpm package(s) if possible. -->
+    <id>xidel</id>
+    <!-- version should MATCH as closely as possible with the underlying software -->
+    <!-- Is the version a prerelease of a version? https://docs.nuget.org/create/versioning#creating-prerelease-packages -->
+    <!-- Note that unstable versions like 0.0.1 can be considered a released version, but it's possible that one can release a 0.0.1-beta before you release a 0.0.1 version. If the version number is final, that is considered a released version and not a prerelease. -->
+    <version>0.9.8</version>
+    <packageSourceUrl>https://github.com/benibela/xidel</packageSourceUrl>
+    <!-- owners is a poor name for maintainers of the package. It sticks around by this name for compatibility reasons. It basically means you. -->
+    <owners>lili</owners>
+    <!-- ============================== -->
+
+    <!-- == SOFTWARE SPECIFIC SECTION == -->
+    <!-- This section is about the software itself -->
+    <title>Xidel</title>
+    <authors>Benito van der Zander</authors>
+    <!-- projectUrl is required for the community feed -->
+    <projectUrl>http://www.videlibri.de/xidel.html</projectUrl>
+    <!--<iconUrl>http://cdn.rawgit.com/__REPLACE_YOUR_REPO__/master/icons/xidel.png</iconUrl>-->
+    <copyright>2019 Xidel videlibri</copyright>
+    <!-- If there is a license Url available, it is required for the community feed -->
+    <licenseUrl>https://github.com/benibela/xidel/blob/master/COPYING</licenseUrl>
+    <requireLicenseAcceptance>false</requireLicenseAcceptance>
+    <projectSourceUrl>https://gitea.miquellionel.ovh/lili/xidel_chocolatey</projectSourceUrl>
+    <docsUrl>https://github.com/benibela/xidel/wiki</docsUrl>
+    <mailingListUrl>https://sourceforge.net/p/videlibri/mailman/</mailingListUrl>
+    <bugTrackerUrl>https://github.com/benibela/xidel/issues</bugTrackerUrl>
+    <tags>xidel html xml json api parser</tags>
+    <summary> Xidel is a command line tool to download and extract data from HTML/XML pages as well as JSON APIs .</summary>
+    <description>---
+    [choco://xidel](choco://xidel)
+    To use choco:// protocol URLs, install [(unofficial) choco:// Protocol support ](https://chocolatey.org/packages/choco-protocol-support)
+    
+    ---
+    
+    It supports:
+
+        Extract expressions:
+
+	- CSS 3 Selectors: to extract simple elements
+	- XPath 3.0: to extract values and calculate things with them
+	- XQuery 3.0: to create new documents from the extracted values
+	- JSONiq: to work with JSON apis
+	- Templates: to extract several expressions in an easy way using a annotated version of the page for pattern-matching
+	- XPath 2.0/XQuery 1.0: compatibility mode for the old XPath/XQuery version
+	    
+	    	Following:
+			
+			- HTTP Codes: Redirections like 30x are automatically followed, while keeping things like cookies
+			- Links: It can follow all links on a page as well as some extracted values
+			- Forms: It can fill in arbitrary data and submit the form
+			    
+			    	Output formats:
+					
+					- Adhoc: just prints the data in a human readable format
+					- XML: encodes the data as XML
+					- HTML: encodes the data as HTML
+					- JSON: encodes the data as JSON
+					- bash/cmd: exports the data as shell variables
+					    
+					    	Connections: HTTP / HTTPS as well as local files or stdin
+						    
+						    	Systems: Windows (using wininet), Linux (using synapse+openssl), Mac (synapse)
+    
+    ---</description>
+    <releaseNotes>http://www.videlibri.de/xidel.html#news</releaseNotes>
+    <!-- =============================== -->      
+
+    <!-- Specifying dependencies and version ranges? https://docs.nuget.org/create/versioning#specifying-version-ranges-in-.nuspec-files -->
+    <!--<dependencies>
+      <dependency id="" version="__MINIMUM_VERSION__" />
+      <dependency id="" version="[__EXACT_VERSION__]" />
+      <dependency id="" version="[_MIN_VERSION_INCLUSIVE, MAX_VERSION_INCLUSIVE]" />
+      <dependency id="" version="[_MIN_VERSION_INCLUSIVE, MAX_VERSION_EXCLUSIVE)" />
+      <dependency id="" />
+      <dependency id="chocolatey-core.extension" version="1.1.0" />
+    </dependencies>-->
+    <!-- chocolatey-core.extension - https://chocolatey.org/packages/chocolatey-core.extension
+         - You want to use Get-UninstallRegistryKey on less than 0.9.10 (in chocolateyUninstall.ps1)
+         - You want to use Get-PackageParameters and on less than 0.11.0
+         - You want to take advantage of other functions in the core community maintainer's team extension package
+    -->
+
+    <!--<provides>NOT YET IMPLEMENTED</provides>-->
+    <!--<conflicts>NOT YET IMPLEMENTED</conflicts>-->
+    <!--<replaces>NOT YET IMPLEMENTED</replaces>-->
+  </metadata>
+  <files>
+    <!-- this section controls what actually gets packaged into the Chocolatey package -->
+    <file src="tools\**" target="tools" />
+    <!--Building from Linux? You may need this instead: <file src="tools/**" target="tools" />-->
+  </files>
+</package>
-- 
cgit v1.2.3-70-g09d2