Skip to content

tunisiano187/Chocolatey-packages

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

Chocolatey Packages

All Contributors jsDelivr Update Pipeline CodeFactor GitHub Activity

This repository contains Chocolatey packages (list) created and maintained by tunisiano that are updated daily.

Patreon

Guidelines

Reporting broken/outdated packages

If packages from this repository fail to install, or a new version has been released by the publisher for a particular package, please report it in any of the following ways:

Broken packages

If the package fails to install or uninstall successfully using Chocolatey (choco), please include a log of the debug output from the terminal for the exact command used:

choco install <package_name> --yes --verbose --debug

Outdated packages

If the package has fallen out-of-date, please include the following information when opening an issue here about if, if possible:

  • The most recent release's:
    • Date
    • Version number/name
    • Known good URL to the installation package

Tags

Learn more about package tags.

Contributing

  1. As much as possible, these packages are maintained automatically by the AU PowerShell module.
  2. If allowed, packages will include the packaged software directly in the .nupkg archive instead of downloading it from the remote source during installation. Only tools that allow redistribution in their license may be embedded this way and such packages must include two additional files in the tools directory:
    • License.txt
    • VERIFICATION.txt
  3. Code is written for humans, not for computers (i.e. Assembly). Make your code submissions readable and adequately commented, but also efficient; the goal is not to obfuscate. If someone else wants to make changes to those files later on, they need to be able to understand what's happening and why, too!
  4. All the metadata attributes in the package needs to be as complete and accurate as possible. If a metadata tag is empty, it is because the information was not available when the package was last reviewed. In instances where important metadata that is not available online should be added to the package, the publisher of the software must first be contacted and give permission to do so in writing.

Contributors ✨

This project follows the All Contributors specification. Contributions of any kind are always welcome!

Thanks go out to these wonderful people (emoji key):

tunisiano187's avatar
Fabian Clerbois

πŸ› πŸ’» πŸ“– 🚧 πŸ“†
amayii0's avatar
Rudy Dullier

πŸ’»
ordonezgs's avatar
Santiago G. OrdoΓ±ez

πŸ’» 🌍
dgalbraith's avatar
D. Galbraith

πŸ’»
gep13's avatar
Gary Ewan Park

πŸ’»
jbarthelmes's avatar
Johannes Barthelmes

πŸ’»
xmha97's avatar
Muhammadhussein Ammari

πŸ’»
RedBaron2's avatar
RB

πŸ›
jwfxpr's avatar
John Reid

πŸ’»
unusedcow's avatar
unusedcow

πŸ’»
pokepoke81's avatar
pokepoke81

πŸ’»
NightFurySL2001's avatar
NightFurySL2001

πŸ’»
brogers5's avatar
Brian Rogers

πŸ’»
blast007's avatar
Scott Wichser

🚧
RogueScholar's avatar
Peter J. Mello

πŸ’» πŸ“– 🚧

About

Chocolatey automatic packages from tunisiano

Resources

License

Code of conduct

Contributing

Security policy

Stars

Watchers

Forks

Packages

No packages published

Contributors 24

Languages