-
Notifications
You must be signed in to change notification settings - Fork 905
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
(tests) Update Test Package to have description
This updates the `test-chocolateypath` package to have a description and removes the unneeded comments. This is related to a GitLab MR that noted these things when bringing this package into the internal repository. This reverts commit ffd9aab4b40dc8b47b84de5f3ce91ea22fda7a6d.
- Loading branch information
Showing
1 changed file
with
2 additions
and
66 deletions.
There are no files selected for viewing
68 changes: 2 additions & 66 deletions
68
tests/packages/test-chocolateypath/test-chocolateypath.nuspec
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,81 +1,17 @@ | ||
| <?xml version="1.0" encoding="utf-8"?> | ||
| <!-- Read this before creating packages: https://docs.chocolatey.org/en-us/create/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://community.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>test-chocolateypath</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.1.0</version> | ||
| <!-- <packageSourceUrl>Where is this Chocolatey package located (think GitHub)? packageSourceUrl is highly recommended for the community feed</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>__REPLACE_YOUR_NAME__</owners>--> | ||
| <!-- ============================== --> | ||
|
|
||
| <!-- == SOFTWARE SPECIFIC SECTION == --> | ||
| <!-- This section is about the software itself --> | ||
| <title>test-packagepath (Install)</title> | ||
| <authors>__REPLACE_AUTHORS_OF_SOFTWARE_COMMA_SEPARATED__</authors> | ||
| <!-- projectUrl is required for the community feed --> | ||
| <projectUrl>https://_Software_Location_REMOVE_OR_FILL_OUT_</projectUrl> | ||
| <!-- There are a number of CDN Services that can be used for hosting the Icon for a package. More information can be found here: https://docs.chocolatey.org/en-us/create/create-packages#package-icon-guidelines --> | ||
| <!-- Here is an example using Githack --> | ||
| <!--<iconUrl>http://rawcdn.githack.com/__REPLACE_YOUR_REPO__/master/icons/test-packagepath.png</iconUrl>--> | ||
| <!-- <copyright>Year Software Vendor</copyright> --> | ||
| <!-- If there is a license Url available, it is required for the community feed --> | ||
| <!-- <licenseUrl>Software License Location __REMOVE_OR_FILL_OUT__</licenseUrl> | ||
| <requireLicenseAcceptance>true</requireLicenseAcceptance>--> | ||
| <!--<projectSourceUrl>Software Source Location - is the software FOSS somewhere? Link to it with this</projectSourceUrl>--> | ||
| <!--<docsUrl>At what url are the software docs located?</docsUrl>--> | ||
| <!--<mailingListUrl></mailingListUrl>--> | ||
| <!--<bugTrackerUrl></bugTrackerUrl>--> | ||
| <tags>test-packagepath SPACE_SEPARATED</tags> | ||
| <summary>__REPLACE__</summary> | ||
| <description>__REPLACE__MarkDown_Okay </description> | ||
| <!-- <releaseNotes>__REPLACE_OR_REMOVE__MarkDown_Okay</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://community.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>--> | ||
| <summary>Package to test the Get-ChocolateyPath Chocolatey PowerShell function.</summary> | ||
| <description>Package to test the Get-ChocolateyPath Chocolatey PowerShell function.</description> | ||
| </metadata> | ||
| <files> | ||
| <!-- this section controls what actually gets packaged into the Chocolatey package --> | ||
| <file src="tools\**" target="tools" /> | ||
| </files> | ||
| </package> |