-
-
Notifications
You must be signed in to change notification settings - Fork 66
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
20 changed files
with
1,856 additions
and
0 deletions.
There are no files selected for viewing
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 |
|---|---|---|
| @@ -0,0 +1,17 @@ | ||
| # <img src="https://cdn.jsdelivr.net/gh/mkevenaar/chocolatey-packages@04dc5eb5743f7aec66c0fd7a583fe56cb80aa51a/icons/helio-workstation.png" width="48" height="48"/> [helio-workstation.install](https://chocolatey.org/packages/helio-workstation.install) | ||
|
|
||
| ##  | ||
| [Helio Workstation](https://helio.fm) is free and open-source music sequencer, designed to be used on all major platforms. | ||
|
|
||
| ## Why another sequencer? | ||
|
|
||
| Most of the DAW interfaces often seem [overcomplicated](http://mashable.com/2015/09/18/german-u-boat/), and they only tend to get more and more bloated over time. Many of them are commercial, proprietary-licensed and almost none of them support all major operating systems at the same time. | ||
|
|
||
| Helio is an attempt to rethink a music sequencer to create a tool that **feels right**. | ||
|
|
||
| It aims to be a modern music creation software, featuring linear-based sequencer with a clean interface, high-performance C++ core, integrated version control providing intelligent synchronization between devices, saved undo history, translations to many languages and more. | ||
|
|
||
|
|
||
| **Please Note**: This is an automatically updated package. If you find it is | ||
| out of date by more than a day or two, please contact the maintainer(s) and | ||
| let them know the package is no longer updating correctly. |
88 changes: 88 additions & 0 deletions
88
automatic/helio-workstation.install/helio-workstation.install.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 |
|---|---|---|
| @@ -0,0 +1,88 @@ | ||
| <?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>helio-workstation.install</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.0</version> | ||
| <!-- owners is a poor name for maintainers of the package. It sticks around by this name for compatibility reasons. It basically means you. --> | ||
| <owners>Maurice Kevenaar</owners> | ||
| <!-- ============================== --> | ||
|
|
||
| <!-- == SOFTWARE SPECIFIC SECTION == --> | ||
| <!-- This section is about the software itself --> | ||
| <title>Helio Workstation (Install)</title> | ||
| <authors>Peter Rudenko</authors> | ||
| <!-- projectUrl is required for the community feed --> | ||
| <projectUrl>https://helio.fm/</projectUrl> | ||
| <iconUrl>https://cdn.jsdelivr.net/gh/mkevenaar/chocolatey-packages@04dc5eb5743f7aec66c0fd7a583fe56cb80aa51a/icons/helio-workstation.png</iconUrl> | ||
| <!-- copyright is usually years and software vendor, but not required for internal feeds --> | ||
| <copyright>Peter Rudenko</copyright> | ||
| <tags>helio-workstation helio admin</tags> | ||
| <releaseNotes>https://github.com/helio-fm/helio-workstation/blob/develop/CHANGELOG.md</releaseNotes> | ||
| <licenseUrl>https://github.com/helio-fm/helio-workstation/blob/develop/LICENSE</licenseUrl> | ||
| <requireLicenseAcceptance>false</requireLicenseAcceptance> | ||
| <packageSourceUrl>https://github.com/mkevenaar/chocolatey-packages/tree/master/automatic/helio-workstation.install</packageSourceUrl> | ||
| <projectSourceUrl>https://github.com/helio-fm/helio-workstation</projectSourceUrl> | ||
| <bugTrackerUrl>https://github.com/helio-fm/helio-workstation/issues</bugTrackerUrl> | ||
| <summary>One music sequencer for all major platforms, desktop and mobile</summary> | ||
| <description>##  | ||
| [Helio Workstation](https://helio.fm) is free and open-source music sequencer, designed to be used on all major platforms. | ||
|
|
||
| ## Why another sequencer? | ||
|
|
||
| Most of the DAW interfaces often seem [overcomplicated](http://mashable.com/2015/09/18/german-u-boat/), and they only tend to get more and more bloated over time. Many of them are commercial, proprietary-licensed and almost none of them support all major operating systems at the same time. | ||
|
|
||
| Helio is an attempt to rethink a music sequencer to create a tool that **feels right**. | ||
|
|
||
| It aims to be a modern music creation software, featuring linear-based sequencer with a clean interface, high-performance C++ core, integrated version control providing intelligent synchronization between devices, saved undo history, translations to many languages and more. | ||
|
|
||
|
|
||
| **Please Note**: This is an automatically updated package. If you find it is | ||
| out of date by more than a day or two, please contact the maintainer(s) and | ||
| let them know the package is no longer updating correctly.</description> | ||
| <!-- =============================== --> | ||
|
|
||
| <!-- 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="" /> | ||
| </dependencies>--> | ||
|
|
||
| <!--<provides>NOT YET IMPLEMENTED</provides>--> | ||
| <!--<conflicts>NOT YET IMPLEMENTED</conflicts>--> | ||
| <!--<replaces>NOT YET IMPLEMENTED</replaces>--> | ||
| </metadata> | ||
| <!-- this section controls what actually gets packaged into the Chocolatey package --> | ||
| <!-- Uncomment to limit what is packed in --> | ||
| <files> | ||
| <file src="tools\**" target="tools" /> | ||
| <file src="legal\**" target="legal" /> | ||
| </files> | ||
| </package> |
Oops, something went wrong.