-
Notifications
You must be signed in to change notification settings - Fork 0
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
16 changed files
with
326 additions
and
568 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 @@ | ||
| /*.nupkg |
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,47 @@ | ||
| ## Ledger Live | ||
|
|
||
| A multi-crypto wallet app to secure thousands of coins and NFTs. [See all supported coins and tokens](https://www.ledger.com/supported-crypto-assets). | ||
|
|
||
|  | ||
|
|
||
| ### Features | ||
|
|
||
| #### Manage your crypto portfolio | ||
|
|
||
| By coupling the Ledger Live wallet app with a Ledger crypto wallet, you can: | ||
|
|
||
| - Securely execute transactions by validating them with your Ledger Hardware Wallet | ||
| - Manage your portfolio as well as 1000s of other crypto assets | ||
| - Track your portfolio | ||
|
|
||
| **Buy, sell, swap, stake, and any other crypto transaction services are provided by third-party service providers.* | ||
|
|
||
| #### Buy crypto | ||
|
|
||
| You can easily buy crypto with a credit/debit card or bank transfer. Choose from a range of service providers – Paypal, Ramp, MoonPay, Sardine – and select the option that works best for you. | ||
|
|
||
| Your crypto will land safely in your Ledger crypto wallet. | ||
|
|
||
| #### Swap crypto | ||
|
|
||
| Swapping allows you to explore different crypto assets, protect your crypto from volatility, and diversify your portfolio. | ||
|
|
||
| You can swap through the Ledger Live app without using fiat currencies. | ||
|
|
||
| #### Stake crypto | ||
|
|
||
| Put your crypto to work and get rewards. | ||
|
|
||
| You can start staking coins through the Ledger Live crypto wallet app. Track your rewards in the Earn section and discover staking opportunities across chains. | ||
|
|
||
| ## Package Notes | ||
|
|
||
| The installer executed by this package was built using Nullsoft Scriptable Install System (NSIS). For advanced setup scenarios, refer to [NSIS's command-line interface documentation](https://nsis.sourceforge.io/Docs/Chapter3.html#installerusage). Any desired arguments can be appended to (or optionally overriding with the `--override-arguments` switch) the package's default install arguments with the `--install-arguments` option. | ||
|
|
||
| --- | ||
|
|
||
| For future upgrade operations, consider opting into Chocolatey's `useRememberedArgumentsForUpgrades` feature to avoid having to pass the same arguments with each upgrade: | ||
|
|
||
| ```shell | ||
| choco feature enable --name="'useRememberedArgumentsForUpgrades'" | ||
| ``` |
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,21 @@ | ||
| MIT License | ||
|
|
||
| Copyright (c) 2024 sublym0nal/brogers5 | ||
|
|
||
| Permission is hereby granted, free of charge, to any person obtaining a copy | ||
| of this software and associated documentation files (the "Software"), to deal | ||
| in the Software without restriction, including without limitation the rights | ||
| to use, copy, modify, merge, publish, distribute, sublicense, and/or sell | ||
| copies of the Software, and to permit persons to whom the Software is | ||
| furnished to do so, subject to the following conditions: | ||
|
|
||
| The above copyright notice and this permission notice shall be included in all | ||
| copies or substantial portions of the Software. | ||
|
|
||
| THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR | ||
| IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, | ||
| FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE | ||
| AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER | ||
| LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, | ||
| OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE | ||
| SOFTWARE. |
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,133 +1,51 @@ | ||
| ## Summary | ||
| How do I create packages? See https://docs.chocolatey.org/en-us/create/create-packages | ||
|
|
||
| If you are submitting packages to the community feed (https://community.chocolatey.org) | ||
| always try to ensure you have read, understood and adhere to the create | ||
| packages wiki link above. | ||
|
|
||
| ## Automatic Packaging Updates? | ||
| Consider making this package an automatic package, for the best | ||
| maintainability over time. Read up at https://docs.chocolatey.org/en-us/create/automatic-packages | ||
|
|
||
| ## Shim Generation | ||
| Any executables you include in the package or download (but don't call | ||
| install against using the built-in functions) will be automatically shimmed. | ||
|
|
||
| This means those executables will automatically be included on the path. | ||
| Shim generation runs whether the package is self-contained or uses automation | ||
| scripts. | ||
|
|
||
| By default, these are considered console applications. | ||
|
|
||
| If the application is a GUI, you should create an empty file next to the exe | ||
| named 'name.exe.gui' e.g. 'bob.exe' would need a file named 'bob.exe.gui'. | ||
| See https://docs.chocolatey.org/en-us/create/create-packages#how-do-i-set-up-shims-for-applications-that-have-a-gui | ||
|
|
||
| If you want to ignore the executable, create an empty file next to the exe | ||
| named 'name.exe.ignore' e.g. 'bob.exe' would need a file named | ||
| 'bob.exe.ignore'. | ||
| See https://docs.chocolatey.org/en-us/create/create-packages#how-do-i-exclude-executables-from-getting-shims | ||
|
|
||
| ## Self-Contained? | ||
| If you have a self-contained package, you can remove the automation scripts | ||
| entirely and just include the executables, they will automatically get shimmed, | ||
| which puts them on the path. Ensure you have the legal right to distribute | ||
| the application though. See https://docs.chocolatey.org/en-us/information/legal. | ||
|
|
||
| You should read up on the Shim Generation section to familiarize yourself | ||
| on what to do with GUI applications and/or ignoring shims. | ||
|
|
||
| ## Automation Scripts | ||
| You have a powerful use of Chocolatey, as you are using PowerShell. So you | ||
| can do just about anything you need. Choco has some very handy built-in | ||
| functions that you can use, these are sometimes called the helpers. | ||
|
|
||
| ### Built-In Functions | ||
| https://docs.chocolatey.org/en-us/create/functions | ||
|
|
||
| A note about a couple: | ||
| * Get-ToolsLocation - used to get you the 'tools' root, which by default is set to 'c:\tools', not the chocolateyInstall bin folder - see https://docs.chocolatey.org/en-us/create/functions/get-toolslocation | ||
| * Install-BinFile - used for non-exe files - executables are automatically shimmed... - see https://docs.chocolatey.org/en-us/create/functions/install-binfile | ||
| * Uninstall-BinFile - used for non-exe files - executables are automatically shimmed - see https://docs.chocolatey.org/en-us/create/functions/uninstall-binfile | ||
|
|
||
| ### Getting package specific information | ||
| Use the package parameters pattern - see https://docs.chocolatey.org/en-us/guides/create/parse-packageparameters-argument | ||
|
|
||
| ### Need to mount an ISO? | ||
| https://docs.chocolatey.org/en-us/guides/create/mount-an-iso-in-chocolatey-package | ||
|
|
||
| ### Environment Variables | ||
| Chocolatey makes a number of environment variables available (You can access any of these with $env:TheVariableNameBelow): | ||
|
|
||
| * TEMP/TMP - Overridden to the CacheLocation, but may be the same as the original TEMP folder | ||
| * ChocolateyInstall - Top level folder where Chocolatey is installed | ||
| * ChocolateyPackageName - The name of the package, equivalent to the `<id />` field in the nuspec | ||
| * ChocolateyPackageTitle - The title of the package, equivalent to the `<title />` field in the nuspec | ||
| * ChocolateyPackageVersion - The normalized version of the package, equivalent to a normalized edition of the `<version />` field in the nuspec | ||
| * ChocolateyPackageFolder - The top level location of the package folder - the folder where Chocolatey has downloaded and extracted the NuGet package, typically `C:\ProgramData\chocolatey\lib\packageName`. | ||
|
|
||
| #### Advanced Environment Variables | ||
| The following are more advanced settings: | ||
|
|
||
| * ChocolateyPackageParameters - Parameters to use with packaging, not the same as install arguments (which are passed directly to the native installer). Based on `--package-parameters`. | ||
| * CHOCOLATEY_VERSION - The version of Choco you normally see. Use if you are 'lighting' things up based on choco version. Otherwise take a dependency on the specific version you need. | ||
| * ChocolateyForceX86 = If available and set to 'true', then user has requested 32bit version. Automatically handled in built in Choco functions. | ||
| * OS_PLATFORM - Like Windows, macOS, Linux. | ||
| * OS_VERSION - The version of OS, like 10.0 something something for Windows. | ||
| * OS_NAME - The reported name of the OS. | ||
| * USER_NAME = The user name | ||
| * USER_DOMAIN = The user domain name (could also be local computer name) | ||
| * IS_PROCESSELEVATED = Is the process elevated? | ||
| * IS_SYSTEM = Is the user the system account? | ||
| * IS_REMOTEDESKTOP = Is the user in a terminal services session? | ||
| * ChocolateyToolsLocation - formerly 'ChocolateyBinRoot' ('ChocolateyBinRoot' will be removed with Chocolatey v2.0.0), this is where tools being installed outside of Chocolatey packaging will go. | ||
|
|
||
| #### Set By Options and Configuration | ||
| Some environment variables are set based on options that are passed, configuration and/or features that are turned on: | ||
|
|
||
| * ChocolateyEnvironmentDebug - Was `--debug` passed? If using the built-in PowerShell host, this is always true (but only logs debug messages to console if `--debug` was passed) | ||
| * ChocolateyEnvironmentVerbose - Was `--verbose` passed? If using the built-in PowerShell host, this is always true (but only logs verbose messages to console if `--verbose` was passed). | ||
| * ChocolateyExitOnRebootDetected - Are we exiting on a detected reboot? Set by ` --exit-when-reboot-detected` or the feature `exitOnRebootDetected` | ||
| * ChocolateyForce - Was `--force` passed? | ||
| * ChocolateyForceX86 - Was `-x86` passed? | ||
| * ChocolateyRequestTimeout - How long before a web request will time out. Set by config `webRequestTimeoutSeconds` | ||
| * ChocolateyResponseTimeout - How long to wait for a download to complete? Set by config `commandExecutionTimeoutSeconds` | ||
| * ChocolateyPowerShellHost - Are we using the built-in PowerShell host? Set by `--use-system-powershell` or the feature `powershellHost` | ||
|
|
||
| #### Business Edition Variables | ||
|
|
||
| * ChocolateyInstallArgumentsSensitive - Encrypted arguments passed from command line `--install-arguments-sensitive` that are not logged anywhere. | ||
| * ChocolateyPackageParametersSensitive - Package parameters passed from command line `--package-parameters-sensitive` that are not logged anywhere. | ||
| * ChocolateyLicensedVersion - What version is the licensed edition on? | ||
| * ChocolateyLicenseType - What edition / type of the licensed edition is installed? | ||
| * USER_CONTEXT - The original user context - different when self-service is used (Licensed) | ||
|
|
||
| #### Experimental Environment Variables | ||
| The following are experimental or use not recommended: | ||
|
|
||
| * OS_IS64BIT = This may not return correctly - it may depend on the process the app is running under | ||
| * CHOCOLATEY_VERSION_PRODUCT = the version of Choco that may match CHOCOLATEY_VERSION but may be different - based on git describe | ||
| * IS_ADMIN = Is the user an administrator? But doesn't tell you if the process is elevated. | ||
| * IS_REMOTE = Is the user in a remote session? | ||
|
|
||
| #### Not Useful Or Anti-Pattern If Used | ||
|
|
||
| * ChocolateyInstallOverride = Not for use in package automation scripts. Based on `--override-arguments` being passed. | ||
| * ChocolateyInstallArguments = The installer arguments meant for the native installer. You should use chocolateyPackageParameters instead. Based on `--install-arguments` being passed. | ||
| * ChocolateyIgnoreChecksums - Was `--ignore-checksums` passed or the feature `checksumFiles` turned off? | ||
| * ChocolateyAllowEmptyChecksums - Was `--allow-empty-checksums` passed or the feature `allowEmptyChecksums` turned on? | ||
| * ChocolateyAllowEmptyChecksumsSecure - Was `--allow-empty-checksums-secure` passed or the feature `allowEmptyChecksumsSecure` turned on? | ||
| * ChocolateyChecksum32 - Was `--download-checksum` passed? | ||
| * ChocolateyChecksumType32 - Was `--download-checksum-type` passed? | ||
| * ChocolateyChecksum64 - Was `--download-checksum-x64` passed? | ||
| * ChocolateyChecksumType64 - Was `--download-checksum-type-x64` passed? | ||
| * ChocolateyPackageExitCode - The exit code of the script that just ran - usually set by `Set-PowerShellExitCode` | ||
| * ChocolateyLastPathUpdate - Set by Chocolatey as part of install, but not used for anything in particular in packaging. | ||
| * ChocolateyProxyLocation - The explicit proxy location as set in the configuration `proxy` | ||
| * ChocolateyDownloadCache - Use available download cache? Set by `--skip-download-cache`, `--use-download-cache`, or feature `downloadCache` | ||
| * ChocolateyProxyBypassList - Explicitly set locations to ignore in configuration `proxyBypassList` | ||
| * ChocolateyProxyBypassOnLocal - Should the proxy bypass on local connections? Set based on configuration `proxyBypassOnLocal` | ||
| * http_proxy - Set by original `http_proxy` passthrough, or same as `ChocolateyProxyLocation` if explicitly set. | ||
| * https_proxy - Set by original `https_proxy` passthrough, or same as `ChocolateyProxyLocation` if explicitly set. | ||
| * no_proxy- Set by original `no_proxy` passthrough, or same as `ChocolateyProxyBypassList` if explicitly set. | ||
| # <img src="https://cdn.jsdelivr.net/gh/brogers5/chocolatey-package-ledger-live@61ab9919bb06f59e0b03ea62e5f7695e1a3d5bbd/ledger-live.png" width="48" height="48"/> Chocolatey Package: [Ledger Live](https://community.chocolatey.org/packages/ledger-live) | ||
|
|
||
| [](https://community.chocolatey.org/packages/ledger-live) | ||
| [](https://community.chocolatey.org/packages/ledger-live) | ||
|
|
||
| ## Install | ||
|
|
||
| [Install Chocolatey](https://chocolatey.org/install), and run the following command to install the latest approved stable version from the Chocolatey Community Repository: | ||
|
|
||
| ```shell | ||
| choco install ledger-live --source="'https://community.chocolatey.org/api/v2'" | ||
| ``` | ||
|
|
||
| Alternatively, the packages as published on the Chocolatey Community Repository (starting with v2.81.2) will also be mirrored on this repository's [Releases page](https://github.com/brogers5/chocolatey-package-ledger-live/releases). The `nupkg` can be installed from the current directory as follows: | ||
|
|
||
| ```shell | ||
| choco install ledger-live --source="'.'" | ||
| ``` | ||
|
|
||
| ## Build | ||
|
|
||
| [Install Chocolatey](https://chocolatey.org/install), clone this repository, and run the following command in the cloned repository: | ||
|
|
||
| ```shell | ||
| choco pack | ||
| ``` | ||
|
|
||
| A successful build will create `ledger-live.x.y.z.nupkg`, where `x.y.z` should be the Nuspec's normalized `version` value at build time. | ||
|
|
||
| >[!Note] | ||
| >Chocolatey package builds are non-deterministic. Consequently, an independently built package's checksum will not match that of the officially published package. | ||
| ## Update | ||
|
|
||
| This package should be automatically updated by the [Chocolatey Automatic Package Updater Module](https://github.com/majkinetor/au), with update queries implemented by the [PowerShellForGitHub PowerShell Module](https://github.com/microsoft/PowerShellForGitHub). If it is outdated by more than a few days, please [open an issue](https://github.com/brogers5/chocolatey-package-ledger-live/issues). | ||
|
|
||
| AU expects the parent directory that contains this repository to share a name with the Nuspec (`ledger-live`). Your local repository should therefore be cloned accordingly: | ||
|
|
||
| ```shell | ||
| git clone git@github.com:brogers5/chocolatey-package-ledger-live.git ledger-live | ||
| ``` | ||
|
|
||
| Alternatively, a junction point can be created that points to the local repository (preferably within a repository adopting the [AU packages template](https://github.com/majkinetor/au-packages-template)): | ||
|
|
||
| ```shell | ||
| mklink /J ledger-live ..\chocolatey-package-ledger-live | ||
| ``` | ||
|
|
||
| Once created, simply run `update.ps1` from within the created directory/junction point. Assuming all goes well, all relevant files should change to reflect the latest version available. This will also build a new package version using the modified files. | ||
|
|
||
| Before submitting a pull request, please [test the package](https://docs.chocolatey.org/en-us/community-repository/moderation/package-verifier#steps-for-each-package) using the latest [Chocolatey Testing Environment](https://github.com/chocolatey-community/chocolatey-test-environment) first. |
Oops, something went wrong.