Could we have a static "latest-release" link? Or a repo with the releases?

[fabiorzfreitas]

Like many other tools, there are lots of users interested in deploying Everything programmatically.

The latest stable release alone had almost 400 000 downloads on Chocolatey!

Nevertheless, I have been informed by other members in this forum that "1.4 is not that great, you should try 1.5". I intend to do so, but I'd also would like to maintain a new Chocolatey 1.5 package, or ask for the implementation of an optional --prerelease switch on the current one.

I've been told that depending on a non-static link, specially if it's inside a forum post, would make it very troublesome for auto-updating a package.

As such, I think that there are a couple of measures that could solve this:

1. The releases (not the source code, but the compiled files) could be available in a repo. Such a repo probably already exists, since every new release is directly hosted on VoidTools.com/x;

2. Given the bottom line's "In Development" link already points to the forum, which then points the download link back to the website, perhaps the website could have an "Alpha" section with the current binaries right next to "In Development".

Thanks for your attention

[void]

I have added the following direct links to the latest 1.5 alpha version:

https://www.voidtools.com/Everything-1.5a.x64-Setup.exe
https://www.voidtools.com/Everything-1.5a.x86-Setup.exe
https://www.voidtools.com/Everything-1.5a.x64.zip
https://www.voidtools.com/Everything-1.5a.x86.zip



Everything 1.5 is still in development.
I will add links to the main page once in beta.

[fabiorzfreitas]

Thank you!

[oleg84]

Like many other tools, there are lots of users interested in deploying Everything programmatically.

The latest stable release alone had almost 400 000 downloads on Chocolatey!

Nevertheless, I have been informed by other members in this forum that "1.4 is not that great, you should try 1.5". I intend to do so, but I'd also would like to maintain a new Chocolatey 1.5 package, or ask for the implementation of an optional --prerelease switch on the current one.

I've been told that depending on a non-static link, specially if it's inside a forum post, would make it very troublesome for auto-updating a package.

As such, I think that there are a couple of measures that could solve this:

1. The releases (not the source code, but the compiled files) could be available in a repo. Such a repo probably already exists, since every new release is directly hosted on VoidTools.com/x;

2. Given the bottom line's "In Development" link already points to the forum, which then points the download link back to the website, perhaps the website could have an "Alpha" section with the current binaries right next to "In Development".

Thanks for your attention

Hey @fabiorzfreitas!

What is the current status of adding Everything 1.5 prerelease to Chocolatey?

I've been using Everything 1.5 for quite a while now.
Recent upgrade of Chocolatey packages (choco upgrade all -y) broke my Everything 1.5 manual installation.
It happened because I install other packages (namely ES) through Choco. And upgrade upgraded all its dependencies including Everything.

Having Everything 1.5 in Choco will help a lot with this.

[fabiorzfreitas]

Hey @fabiorzfreitas!

What is the current status of adding Everything 1.5 prerelease to Chocolatey?

I've been using Everything 1.5 for quite a while now.
Recent upgrade of Chocolatey packages (choco upgrade all -y) broke my Everything 1.5 manual installation.
It happened because I install other packages (namely ES) through Choco. And upgrade upgraded all its dependencies including Everything.

Having Everything 1.5 in Choco will help a lot with this.

Hi, @oleg84,

I had plans to work on multiple Chocolatey packages for a bunch of software I use, but are not available there.

Unfortunately, I've had some major setbacks in my personal life, so this project of mine is indefinitely delayed.

Still, I've gone as far as gathering every resource needed for it on this GitHub comment:

I think you'll find everything you'll need here:

• The Chocolatey Automatic Package Updater Module repo;
• The documentation pages that
  readme.md
  should be pointing to, on Chocolatey and the original wiki;
• And the linked video-tutorial.

Please note that even if

readme.md

has a broken link and a warning/disclaimer on top, this fork (from the user created original, and endorsed by Chocolatey) has been made in 2022, since its owner would/could not maintain it anymore.


As of March 2024, the Chocolatey Team released the new 1.0.0 version and announced the process of deprecating the original (and still functional) tool.

This is certainly on my TODO list, but I cannot say if I'll be working on it next month or next year :p