Recently I found an equivalent to "apt-get" for Windows, Chocolatey is The Package Manager for Windows, you can install, upgrade, uninstall multiple programs at the same time, like apt-get, some examples: ... https://chocolatey.org/packages/blender $ choco install blender https://chocolatey.org/packages/freecad/0.19.0.22366-dev $ choco install Freecad --pre https://chocolatey.org/packages/sweet-home-3d $ choco install sweet-home-3d ... ... and this is not just for programs because add-on, plug-ing, script, macros, complements, extensions, etc, can be managed from there. in context, if a windows user wants to update their programs, need open each URL and download individually each program and this can be a pain, with choco you just need do this: choco upgrade all -y ... could be a help for new users. request: *add a choco installer* ... https://chocolatey.org/packages/libreoffice $ choco install libreoffice https://chocolatey.org/packages/libreoffice-pree $ choco install libreoffice --pre ...
It looks like LibreOffice 6.4.6 is already available at this URL: https://chocolatey.org/packages/libreoffice-fresh And LibreOffice 6.3.6 is available at this URL: https://chocolatey.org/packages/libreoffice-still The maintainer of these packages seems to be this person: https://chocolatey.org/profiles/wget I'm not clear on what you are asking for from the LibreOffice developer community.
From my perspective not a bug/enhancement request for LibreOffice developers but for chocolatey.org package maintainers.
I agree, everything depend by Chocolatey maintainer. So this is not our bug. And also everything is well updated on their repositories. Resolved.
Normal questions of quality and adulteration of the installer come to mind. But as with Flatpack, Snap, Appimage packaging, don't see why Choclatey/NuGet packaging for a LO Windows installer couldn't be listed on the projects Download page [1] if the maintainer is interested. @William? Likewise as MS' current "Windows Package Manager" 'winget' project gains traction, LibreOffice might consider participating in that package mechanism (assuming LO acceptance of its support of Windows 10 and later only). Otherwise our .msi packages, our network of mirrors, and normal MS Installer deployments remains quite functional. And it is fine for this to end with a WONTFIX =-ref-= [1] https://libreoffice.org/download/download/
1.- My request is about of add an official LO maintainer, chocolatey actually is not updated and the actual maintainer is afk, the LO packages was marked as Deprecated for inactivity. 2.- I was redirected since the LO-ask forum: https://ask.libreoffice.org/en/question/265651/request-add-cli-installer-manager-for-windows/ 3.- Windows Package Manager is being developed, but is still green, for this I was requesting a Chocolatey official installer, especially when actually LO has not am an auto-updater.
"1.- My request is about of add an official LO maintainer, chocolatey actually is not updated and the actual maintainer is afk, the LO packages was marked as Deprecated for inactivity." Hi there. I'm afraid, this statement is not true :P Since I took over maintenance of that package and I proceeded to its complete rewrite, it is automated for a bunch of time now. cf. https://chocolatey.org/packages/libreoffice-fresh#comment-4660033936 It is relying on the TDF update service to detect whether updates exist or not. So if you are not seeing any updates there, this is because TDF hadn't opened the tap yet ;-) cf. https://listarchives.libreoffice.org/global/website/2020/msg00319.html It should now be automated from TDF as well. As per today's infra meeting, the sysadmin team confirmed to me that after a few days after a new release launch, the update service will be populated with the latest hashes corresponding to the latest versions ^^
Looks like this can be closed