oneget
au
oneget | au | |
---|---|---|
3 | 4 | |
2,307 | 220 | |
- | - | |
1.1 | 4.3 | |
over 2 years ago | over 1 year ago | |
C# | PowerShell | |
MIT License | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
oneget
-
just got a new laptop i don't know what's the important apps to install?
Chocolatey can only manage things installed by Chocolatey. If you use Powershell's PackageManagement functionality (which is a "package manager manager") then you can integrate Chocolatey with a handful of other (also usually nuget-based) package managers, but you're still fundamentally limited to "can only manage what was installed by the manager" behavior.
- Announcing Windows Package Manager version 1.0 | Windows Command Line
- WinGet is terrible. I want AppGet back
au
-
So according to Repology, Nix has an insane lead on available packages, but somehow has around a tenth of AURs maintainers. How does Nix also manage to be the most up to date?
I created au framework for chocolatey (Windows OS) and on packages that are cross platform, it made choco above Arch on freshness: https://github.com/majkinetor/au
-
Is there some centralized source to get the most recent version numbers of often used software?
Having said that, you may want to look into the source code for each package you're interested in. Many of them use the Chocolatey Automatic Package Updater Module, and had to solve this exact problem in some way to help automate updates. I've seen approaches varying from scraping a web page, querying an API, or even downloading the binary and looking at its FileVersionInfo struct.
-
Novice to Package Managers, Interested in Chocolatey
There are a lot of packages out there where you can customise the install location. If you want to automatically fetch from suppliers and create your own packages then you probably want to look at the automatic package updater with AppVeyor: https://github.com/majkinetor/au/wiki
-
WinGet is terrible. I want AppGet back
> I mean, it is a chocolatey, because they allow multiple packaged for the same software.
I think this is more healthy then having one with maintainers refusing to do stuff you may need. The real thing would be for vendors releasing packages but we are far from that in Windows land.
> I meant that packages are often not updated by the maintainers.
Yeah, that was the problem far more before then today. I created AU to solve that issue [1].
[1]: https://github.com/majkinetor/au
What are some alternatives?
winget-cli - WinGet is the Windows Package Manager. This project includes a CLI (Command Line Interface), PowerShell modules, and a COM (Component Object Model) API (Application Programming Interface).
Versions - 📦 A Scoop bucket for alternative versions of apps.
Chocolatey - Chocolatey - the package manager for Windows
ChocoButler - ChocoButler - an automatic updater for Chocolatey
winget-pkgs - The Microsoft community Windows Package Manager manifest repository
wixsharp - Framework for building a complete MSI or WiX source code by using script files written with C# syntax.
Scoop-Core - Shovel. Alternative, more advanced, and user-friendly implementation of windows command-line installer scoop.
wix3 - WiX Toolset v3.x
OSD - OSD Shared Functions
Shovel-Ash258 - Personal Shovel bucket with a wide variety of applications of all kinds.
ts_block - Blocks IP addresses generating invalid Terminal Services logons