From 6fc1b5303957e43f682c24953dc1399892e98357 Mon Sep 17 00:00:00 2001 From: 1kamma Date: Wed, 15 Jul 2020 16:36:40 +0300 Subject: [PATCH] first commit --- ReadMe.md | 134 ++++++++++++++++++++++++++++++++++++ _TODO.txt | 131 +++++++++++++++++++++++++++++++++++ cpod.1.27.1.nupkg | Bin 0 -> 2522 bytes cpod.nuspec | 79 +++++++++++++++++++++ tools/chocolateyinstall.ps1 | 40 +++++++++++ 5 files changed, 384 insertions(+) create mode 100644 ReadMe.md create mode 100644 _TODO.txt create mode 100644 cpod.1.27.1.nupkg create mode 100644 cpod.nuspec create mode 100644 tools/chocolateyinstall.ps1 diff --git a/ReadMe.md b/ReadMe.md new file mode 100644 index 0000000..da7393d --- /dev/null +++ b/ReadMe.md @@ -0,0 +1,134 @@ +## Summary +How do I create packages? See https://chocolatey.org/docs/create-packages + +If you are submitting packages to the community feed (https://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://chocolatey.org/docs/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://chocolatey.org/docs/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://chocolatey.org/docs/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://chocolatey.org/docs/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://chocolatey.org/docs/helpers-reference + +A note about a couple: +* Get-BinRoot - this is a horribly named function that doesn't do what new folks think it does. It gets you the 'tools' root, which by default is set to 'c:\tools', not the chocolateyInstall bin folder - see https://chocolatey.org/docs/helpers-get-tools-location +* Install-BinFile - used for non-exe files - executables are automatically shimmed... - see https://chocolatey.org/docs/helpers-install-bin-file +* Uninstall-BinFile - used for non-exe files - executables are automatically shimmed - see https://chocolatey.org/docs/helpers-uninstall-bin-file + +### Getting package specific information +Use the package parameters pattern - see https://chocolatey.org/docs/how-to-parse-package-parameters-argument + +### Need to mount an ISO? +https://chocolatey.org/docs/how-to-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 `` field in the nuspec (0.9.9+) + * ChocolateyPackageTitle - The title of the package, equivalent to the `` field in the nuspec (0.10.1+) + * ChocolateyPackageVersion - The version of the package, equivalent to the `<version />` field in the nuspec (0.9.9+) + * 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`. (0.9.8.22+) + * CHOCOLATEY_VERSION - The version of Choco you normally see. Use if you are 'lighting' things up based on choco version. (0.9.9+) - Otherwise take a dependency on the specific version you need. + * ChocolateyForceX86 = If available and set to 'true', then user has requested 32bit version. (0.9.9+) - Automatically handled in built in Choco functions. + * OS_PLATFORM - Like Windows, OSX, Linux. (0.9.9+) + * OS_VERSION - The version of OS, like 6.1 something something for Windows. (0.9.9+) + * OS_NAME - The reported name of the OS. (0.9.9+) + * USER_NAME = The user name (0.10.6+) + * USER_DOMAIN = The user domain name (could also be local computer name) (0.10.6+) + * IS_PROCESSELEVATED = Is the process elevated? (0.9.9+) + * IS_SYSTEM = Is the user the system account? (0.10.6+) + * IS_REMOTEDESKTOP = Is the user in a terminal services session? (0.10.6+) + * ChocolateyToolsLocation - formerly 'ChocolateyBinRoot' ('ChocolateyBinRoot' will be removed with Chocolatey v2.0.0), this is where tools being installed outside of Chocolatey packaging will go. (0.9.10+) + +#### 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) (0.9.10+) + * 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). (0.9.10+) + * ChocolateyForce - Was `--force` passed? (0.9.10+) + * ChocolateyForceX86 - Was `-x86` passed? (CHECK) + * ChocolateyRequestTimeout - How long before a web request will time out. Set by config `webRequestTimeoutSeconds` (CHECK) + * ChocolateyResponseTimeout - How long to wait for a download to complete? Set by config `commandExecutionTimeoutSeconds` (CHECK) + * ChocolateyPowerShellHost - Are we using the built-in PowerShell host? Set by `--use-system-powershell` or the feature `powershellHost` (0.9.10+) + +#### Business Edition Variables + + * ChocolateyInstallArgumentsSensitive - Encrypted arguments passed from command line `--install-arguments-sensitive` that are not logged anywhere. (0.10.1+ and licensed editions 1.6.0+) + * ChocolateyPackageParametersSensitive - Package parameters passed from command line `--package-parameters-senstivite` that are not logged anywhere. (0.10.1+ and licensed editions 1.6.0+) + * 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 v1.10.0+) + +#### 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 (0.9.9+) + * CHOCOLATEY_VERSION_PRODUCT = the version of Choco that may match CHOCOLATEY_VERSION but may be different (0.9.9+) - based on git describe + * IS_ADMIN = Is the user an administrator? But doesn't tell you if the process is elevated. (0.9.9+) + * IS_REMOTE = Is the user in a remote session? (0.10.6+) + +#### Not Useful Or Anti-Pattern If Used + + * ChocolateyInstallOverride = Not for use in package automation scripts. Based on `--override-arguments` being passed. (0.9.9+) + * ChocolateyInstallArguments = The installer arguments meant for the native installer. You should use chocolateyPackageParameters instead. Based on `--install-arguments` being passed. (0.9.9+) + * ChocolateyIgnoreChecksums - Was `--ignore-checksums` passed or the feature `checksumFiles` turned off? (0.9.9.9+) + * ChocolateyAllowEmptyChecksums - Was `--allow-empty-checksums` passed or the feature `allowEmptyChecksums` turned on? (0.10.0+) + * ChocolateyAllowEmptyChecksumsSecure - Was `--allow-empty-checksums-secure` passed or the feature `allowEmptyChecksumsSecure` turned on? (0.10.0+) + * ChocolateyCheckLastExitCode - Should Chocolatey check LASTEXITCODE? Is the feature `scriptsCheckLastExitCode` turned on? (0.10.3+) + * ChocolateyChecksum32 - Was `--download-checksum` passed? (0.10.0+) + * ChocolateyChecksumType32 - Was `--download-checksum-type` passed? (0.10.0+) + * ChocolateyChecksum64 - Was `--download-checksum-x64` passed? (0.10.0)+ + * ChocolateyChecksumType64 - Was `--download-checksum-type-x64` passed? (0.10.0)+ + * ChocolateyPackageExitCode - The exit code of the script that just ran - usually set by `Set-PowerShellExitCode` (CHECK) + * 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` (0.9.9.9+) + * ChocolateyDownloadCache - Use available download cache? Set by `--skip-download-cache`, `--use-download-cache`, or feature `downloadCache` (0.9.10+ and licensed editions 1.1.0+) + * ChocolateyProxyBypassList - Explicitly set locations to ignore in configuration `proxyBypassList` (0.10.4+) + * ChocolateyProxyBypassOnLocal - Should the proxy bypass on local connections? Set based on configuration `proxyBypassOnLocal` (0.10.4+) + * http_proxy - Set by original `http_proxy` passthrough, or same as `ChocolateyProxyLocation` if explicitly set. (0.10.4+) + * https_proxy - Set by original `https_proxy` passthrough, or same as `ChocolateyProxyLocation` if explicitly set. (0.10.4+) + * no_proxy- Set by original `no_proxy` passthrough, or same as `ChocolateyProxyBypassList` if explicitly set. (0.10.4+) + +"# copdchoco" diff --git a/_TODO.txt b/_TODO.txt new file mode 100644 index 0000000..80d5a01 --- /dev/null +++ b/_TODO.txt @@ -0,0 +1,131 @@ +TODO + +1. Determine Package Use: + + Organization? Internal Use? - You are not subject to distribution + rights when you keep everything internal. Put the binaries directly + into the tools directory (as long as total nupkg size is under 1GB). + When bigger, look to use from a share or download binaries from an + internal location. Embedded binaries makes for the most reliable use + of Chocolatey. Use `$fileLocation` (`$file`/`$file64`) and + `Install-ChocolateyInstallPackage`/`Get-ChocolateyUnzip` in + tools\chocolateyInstall.ps1. + + You can also choose to download from internal urls, see the next + section, but ignore whether you have distribution rights or not, it + doesn't apply. Under no circumstances should download from the + internet, it is completely unreliable. See + https://chocolatey.org/docs/community-packages-disclaimer#organizations + to understand the limitations of a publicly available repository. + + Community Repository? + Have Distribution Rights? + If you are the software vendor OR the software EXPLICITLY allows + redistribution and the total nupkg size will be under 200MB, you + have the option to embed the binaries directly into the package to + provide the most reliable install experience. Put the binaries + directly into the tools folder, use `$fileLocation` (`$file`/ + `$file64`) and `Install-ChocolateyInstallPackage`/ + `Get-ChocolateyUnzip` in tools\chocolateyInstall.ps1. Additionally, + fill out the LICENSE and VERIFICATION file (see 3 below and those + files for specifics). + + NOTE: You can choose to download binaries at runtime, but be sure + the download location will remain stable. See the next section. + + Do Not Have Distribution Rights? + - Note: Packages built this way cannot be 100% reliable, but it's a + constraint of publicly available packages and there is little + that can be done to change that. See + https://chocolatey.org/docs/community-packages-disclaimer#organizations + to better understand the limitations of a publicly available + repository. + Download Location is Publicly Available? + You will need to download the runtime files from their official + location at runtime. Use `$url`/`$url64` and + `Install-ChocolateyPackage`/`Install-ChocolateyZipPackage` in + tools\chocolateyInstall.ps1. + Download Location is Not Publicly Available? + Stop here, you can't push this to the community repository. You + can ask the vendor for permission to embed, then include a PDF of + that signed permission directly in the package. Otherwise you + will need to seek alternate locations to non-publicly host the + package. + Download Location Is Same For All Versions? + You still need to point to those urls, but you may wish to set up + something like Automatic Updater (AU) so that when a new version + of the software becomes available, the new package version + automatically gets pushed up to the community repository. See + https://chocolatey.org/docs/automatic-packages#automatic-updater-au + +2. Determine Package Type: + +- Installer Package - contains an installer (everything in template is + geared towards this type of package) +- Zip Package - downloads or embeds and unpacks archives, may unpack + and run an installer using `Install-ChocolateyInstallPackage` as a + secondary step. +- Portable Package - Contains runtime binaries (or unpacks them as a + zip package) - cannot require administrative permissions to install + or use +- Config Package - sets config like files, registry keys, etc +- Extension Package - Packages that add PowerShell functions to + Chocolatey - https://chocolatey.org/docs/how-to-create-extensions +- Template Package - Packages that add templates like this for `choco + new -t=name` - https://chocolatey.org/docs/how-to-create-custom-package-templates +- Other - there are other types of packages as well, these are the main + package types seen in the wild + +3. Fill out the package contents: + +- tools\chocolateyBeforeModify.ps1 - remove if you have no processes + or services to shut down before upgrade/uninstall +- tools\LICENSE.txt / tools\VERIFICATION.txt - Remove if you are not + embedding binaries. Keep and fill out if you are embedding binaries + in the package AND pushing to the community repository, even if you + are the author of software. The file becomes easier to fill out + (does not require changes each version) if you are the software + vendor. If you are building packages for internal use (organization, + etc), you don't need these files as you are not subject to + distribution rights internally. +- tools\chocolateyUninstall.ps1 - remove if autouninstaller can + automatically uninstall and you have nothing additional to do during + uninstall +- Readme.txt - delete this file once you have read over and used + anything you've needed from here +- nuspec - fill this out, then clean out all the comments (you may wish + to leave the headers for the package vs software metadata) +- tools\chocolateyInstall.ps1 - instructions in next section. + +4. ChocolateyInstall.ps1: + +- For embedded binaries - use `$fileLocation` (`$file`/`$file64`) and + `Install-ChocolateyInstallPackage`/ `Get-ChocolateyUnzip`. +- Downloading binaries at runtime - use `$url`/`$url64` and + `Install-ChocolateyPackage` / `Install-ChocolateyZipPackage`. +- Other needs (creating files, setting registry keys), use regular + PowerShell to do so or see if there is a function already defined: + https://chocolatey.org/docs/helpers-reference +- There may also be functions available in extension packages, see + https://chocolatey.org/packages?q=id%3A.extension for examples and + availability. +- Clean out the comments and sections you are not using. + +5. Test the package to ensure install/uninstall work appropriately. + There is a test environment you can use for this - + https://github.com/chocolatey/chocolatey-test-environment + +6. Learn more about Chocolatey packaging - go through the workshop at + https://github.com/ferventcoder/chocolatey-workshop + You will learn about + - General packaging + - Customizing package behavior at runtime (package parameters) + - Extension packages + - Custom packaging templates + - Setting up an internal Chocolatey.Server repository + - Adding and using internal repositories + - Reporting + - Advanced packaging techniques when installers are not friendly to + automation + +7. Delete this file. diff --git a/cpod.1.27.1.nupkg b/cpod.1.27.1.nupkg new file mode 100644 index 0000000000000000000000000000000000000000..a38421340f8b6256775950b7d46ae386f2f4ae46 GIT binary patch literal 2522 zcmcImc{tQv8y*ZI5i@o|=p`~^8N_P~Sq6<QFT-ezu?=RL8RWH>rPm%p$T}+fCnRej zOUZ<Uv5hT?EGcD4zUg}ZX!+jn`|msFI_F%!-#O2HuIqX3`*{um&H@Aj0DvO^mFNwG z#5PALm<a&bVvM7Vzpg~AFA1XbZO*tc;L`;?9=#FMer-?(Ma#^iJmHYt8N|IgdVPC> zHz_<dW3WBU-b=CwJh5<Jn@)x1PPgdP9_@B-T@7~Op!O9>B;|&LQ(wAu2Tk_I4MbUK zW#y99q-swR%a(idx<LA!(vG)JOZ43wSS)$flz2I|@V(^=VA65%CrCDkUC;W%ciYl~ zJmoN<ur1r_!Abn3%MPgxfLdV1?OSqKDk>mP{<9c#r<S-3K5{lhI3#?03@6L}itC&? zEk09qXZ0|mlo{@rqJ`6!@aA>1?)8<Me%MkD>P|4&b73hjYq^;0mq2+<K`e~O56RQ2 zVw}|bPs?b#J@l~KMwJyI8?M=`E)Op{^c<VAZ#)130EdSx0K`wudsiN!D#;80th4;> zJPZNvuH+v;B49C;^l6_-D7bfnJ%s&6#W9=yOunZllHm@|yf`Kc6Fb(yZ#9QJ;Q2B& zYbZa#5K3F86(2j%R_J-B<n0e*7lwCtKCA|X?T!a6vPXNhAqV0W3wQ|=qN@)oXxS49 z#6VhWs5Osyge_81F6c6BvQ(|LNNq*@<7tn!R~;twI~M!-CmKu(6(PhN_)3pvB=tne zEvdxR<~T~C`O3dK8(>K%TFd0EPQ4_T-RaAI9-osxnyyV7F(4fbiEgcoc2k<y11wWU z&5C>KKS-(LJDPqY)-Y3Y@)Og0^fVXMT{C9NHjUQpcy6?c+COfwXg3p{-S=XttYQ<K zGsg*~5k+z?2JrgqRYpwE#l;KGjlC-oR1QVv1}-ceuPYE-mY9B&;IH+lNN5HaRgJH~ z&(P^3AGuVc;$|ORwL0XkeoM==Wv&le23Gx9Ag+vwj+_CmXQQ}naF{Ku_mys^CMX}L ze8qsx^*mMkT9q+lYa8oltjW&A>OcCOI=asRSe^n`V!$_@q53!lE+Sa<1^1LfR_APu z^|4~U^U$V@yoS6FrL(Q`a1^lvK2pri@1#gTiSI<-CCW!X;mk#8=}hU5bZ~pSIyuNp zgul6Dr5+jJHd!nE$4wDi{Sj#DDEk&oYe8Z@@1uFd!vfH2E=Qz>t_MuV({e}ila9b> zM9GCb+wBU!-^tH8u9iO15YI`-4-j118*dtLWoYbYA`#N42$kr2vVSoYh-HvTlyQQL z$1_xj@xo*9zGyNw*xR2(M*I3I5lG5dgbTb23J!yO)B_4zbca*cPTB%n9<Uf-p%S4< zYtteYxoMP_mR~kbt$~LGwg}X=<tdW0r;Vw+yOYnUiJQ^KOugXx8eYw##kr^!s?pI7 zd#cPiHr-o!)!Nkh#^UDlD3gKK^XYL1E-fJ029>W}x*$u#$!9OnT}~byb)b?FxD}tY zs+=XRN;`lbh`h7<wHsm#5^JTqrdAp8o6hR<-z((9pAoF*3>;5U3j2L<MubccmY(m@ zws7gy45$w+MVh|8C|ohgGiLDSy3R0L56ioDVUv4!p2`-ze0+96U*;5)`@%kTJrUPU zQue2*K`bIbnBQ?JseGab9?ijG&y!KhU4EHLI5}5)dZM3@$b#5!b9qJ-Nhx^&I3E>~ zrJPJsffIC*M$tyrwQ}=nmL;;(PPv5lVhf5FY(H?ZhgD4A%-rnkElY%jop~p$spa#x z-&)ueTFBp>V~scTMOpBLE@>46ZdTjp5ZAE{a;$enK2_9ekoPM_l>6xP*xi(Hrk_*6 za{3N&gb}$RMifDe6={g~Cu9A|u6Dr$EXhUbil1-Z4FjJpeJ<nAF*E4F2jdH5YxCN4 z<6O~?%-0kr4cCN~(+r9Gr_CH<Vh2mF93D0zTC|nwv=KM5ZP|01nM^oH5--O)$_=+U zTh<l~_k-Q|Jm+M@Ey}+vwapsAQ?*oOr45zf2<`qiXJ;LRp6Y1~B=qKGq+R@T27n}0 z9~4Se)-@jt4ceo;1PB{ro3t^5OZn1luyvlYLu`4tVgn2!eCuR?I_u+IJ(waq<%=Hg z(m8&?5@YG<qKT<Zce`Qac0DI(rg3nuKkfnjKWO}|m}oeHQj!=BNN3R4nsI`F#^BJN zSO^JA4D`leNf19Q8SRcHqaheP5qpL}#1pVYvNvM`rlPE_s^+e$iov4QJYX0!#zP$j zRfnmmpM}CSR5TdO_jAV(d~N#uC!xn%1>fi$*XpP6cL&azbLN~NdJPK^hCZ36E5t#K z`4;crKWyhhE1Vyc_VkS1&tCef>9r*oiWsdoHeP0BlCHG#pbPNs(_Ajo!@iCjSw$~Y zv7~S^o1F%Y+SGR|6eCraipNIwbkeUz#WHcRT^x$%2MKoY%ssm5d@H-R@YJYgGPzQ9 z!$Y@bykPlm)s>j27a1IVNs)CvHqp-9Y7IU%rH$dULievN%s>9Txm54YBAF$2HYC?~ z>CRBR+8L=NFm5iYWP6%Lh;$OU&LkQb<9dbf>gF@_#HG(SfiTTuvNWcYdwci(s<YXQ zjMg@>(Ozs+8BQ*eVG)E(rV*r{rmMU+tvhI#etlH-rLKL=<Dio?><oXV_p)>#f1Be_ zIXWvy>BOv>6T~pnRm*1_=$U3UPSOh7%HX-XZW0Ql<hIs><I=up^|~84kgXhKcLiYQ zd8(qW=dY&u&RZ$G7q`+|W3oUxw6wP)6`Lxv8WE6owRc?-@{YTJjiHsVj0pdo!kC!B zfdBrKU=ZMk_QS&h0sq<X*E0IuN{4aP4@LDy!+%Pf-wk6K75RT8(I0`n5%*X1eg`sT l{YNeT3h*oQzXMpZ{U3CIfU`1S0RUD;4`KMo?8vvTe*+-`DuMt2 literal 0 HcmV?d00001 diff --git a/cpod.nuspec b/cpod.nuspec new file mode 100644 index 0000000..294feee --- /dev/null +++ b/cpod.nuspec @@ -0,0 +1,79 @@ +<?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>cpod</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>1.27.1</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>CPod (Install) + __REPLACE_AUTHORS_OF_SOFTWARE_COMMA_SEPARATED__ + + https://_Software_Location_REMOVE_OR_FILL_OUT_ + + + + + + + + + cpod podcast + A simple, beautiful podcast app for Windows, macOS, and Linux. + + + + + + + + + + + + + + + + + diff --git a/tools/chocolateyinstall.ps1 b/tools/chocolateyinstall.ps1 new file mode 100644 index 0000000..6165aed --- /dev/null +++ b/tools/chocolateyinstall.ps1 @@ -0,0 +1,40 @@ + +$ErrorActionPreference = 'Stop'; +$toolsDir = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)" +$url64 = 'https://github.com/z-------------/CPod/releases/download/v1.27.1/CPod-Setup-1.27.1.exe' + +$packageArgs = @{ + packageName = 'CPod' + unzipLocation = $toolsDir + fileType = 'EXE' + url64bit = $url64 + + softwareName = 'CPod*' + + + checksum64 = '11D1409626E606EBF6097F313D6541D5B26622EBE3AAA2F1C02C31911CDAA1CD' + checksumType64= 'sha256' + + validExitCodes= @(0, 3010, 1641) +} + +Install-ChocolateyPackage @packageArgs + + + + + + + + + + + + + + + + + + +