You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
**NOTE**: This is an automatically updated package. If you find it is out of date by more than a week, please contact the maintainer(s) and let them know the package is no longer updating correctly.
<!-- Read this before creating packages: https://chocolatey.org/docs/create-packages -->
3
+
<!-- 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). -->
4
+
<!-- Test your packages in a test environment: https://github.com/chocolatey/chocolatey-test-environment -->
5
+
<!--
6
+
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:
7
+
* the package xmlns schema url may cause issues with nuget.exe
8
+
* Any of the following elements can ONLY be used by choco tools - projectSourceUrl, docsUrl, mailingListUrl, bugTrackerUrl, packageSourceUrl, provides, conflicts, replaces
9
+
* nuget.exe can still install packages with those elements but they are ignored. Any authoring tools or commands will error on those elements
10
+
-->
11
+
<!-- You can embed software files directly into packages, as long as you are not bound by distribution rights. -->
12
+
<!-- * If you are an organization making private packages, you probably have no issues here -->
13
+
<!-- * If you are releasing to the community feed, you need to consider distribution rights. -->
<!-- This section is about this package, although id and version have ties back to the software -->
18
+
<!-- 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 -->
19
+
<!-- If the software is cross-platform, attempt to use the same id as the debian/rpm package(s) if possible. -->
20
+
<id>sqlite-studio.install</id>
21
+
<!-- version should MATCH as closely as possible with the underlying software -->
22
+
<!-- Is the version a prerelease of a version? https://docs.nuget.org/create/versioning#creating-prerelease-packages -->
23
+
<!-- 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. -->
**NOTE**: This is an automatically updated package. If you find it is out of date by more than a week, please contact the maintainer(s) and let them know the package is no longer updating correctly.
49
+
</description>
50
+
<!-- <releaseNotes></releaseNotes> -->
51
+
<!-- =============================== -->
52
+
<!-- Specifying dependencies and version ranges? https://docs.nuget.org/create/versioning#specifying-version-ranges-in-.nuspec-files -->
<!-- chocolatey-uninstall.extension - If supporting 0.9.9.x (or below) and including a chocolateyUninstall.ps1 file to uninstall an EXE/MSI, you probably want to include chocolatey-uninstall.extension as a dependency. Please verify whether you are using a helper function from that package. -->
62
+
<!--<provides>NOT YET IMPLEMENTED</provides>-->
63
+
<!--<conflicts>NOT YET IMPLEMENTED</conflicts>-->
64
+
<!--<replaces>NOT YET IMPLEMENTED</replaces>-->
65
+
</metadata>
66
+
<files>
67
+
<!-- this section controls what actually gets packaged into the Chocolatey package -->
68
+
<filesrc="tools\**"target="tools" />
69
+
<!--Building from Linux? You may need this instead: <file src="tools/**" target="tools" />-->
0 commit comments