Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update version on Chocolatey #959

Closed
corydeppen opened this issue May 21, 2016 · 11 comments
Closed

Update version on Chocolatey #959

corydeppen opened this issue May 21, 2016 · 11 comments

Comments

@corydeppen
Copy link

I was wondering if there is anyone actively working on updating the versions of cmder on Chocolatey.

The current version that's available on Chocolatey (1.1.4.1) has an updater that is now broken with the following error because the conemu repository has moved.

---------------------------
ConEmu 140707 [32]
---------------------------
Version update information is broken (not found)
[ConEmu_Stable_2] "version"

http://conemu-maximus5.googlecode.com/
svn/trunk/ConEmu/version.ini

Error code=2
---------------------------
OK
---------------------------
@MartiUK
Copy link
Member

MartiUK commented May 26, 2016

We have not and will not support the version in chocolatey. Please download the latest version on GitHub.

@artisticcheese
Copy link

Please use chocolatey for distribution. Big number of Windows admins are about to endavour of WMF5 package management which will eventually lead them to Chocolatey repo.

@corydeppen
Copy link
Author

Yeah, I'm a bit curious why there's an aversion to updating cmder on Chocolatey. A "...have not and will not support..." stance seems to be an odd choice given the benefits Chocolatey offers and the community support behind it. Would be helpful to understand the reasoning behind the decision.

@daxgames
Copy link
Member

daxgames commented Jun 7, 2016

There is no need to use Choclatey to install cmder, there is no install process. Download, unzip, done!

Just my $.02.

@artisticcheese
Copy link

There is a need for chocolatey for bunch of scenarios, one of them is automation. For example if you use Chef there is chocolatey cookbook which will allow you to specify list of software you want your servers to have installed and keep updated.

@jankatins
Copy link
Contributor

As far as I can see choco devs for cmder are not the same as the devs for cmder itself, so I think it's easiest to ask the choco devs to build new package instead of here.

And thats possible happening here: https://chocolatey.org/packages/Cmder/1.3.0-beta

@Jackbennett
Copy link
Contributor

You should be using PS Remoting for your servers not using remote desktop with cmder on there.

@MartiUK
Copy link
Member

MartiUK commented Jun 7, 2016

It’s up to the package maintainer to package it for chocolatey, not us.

Martin

@dtgm
Copy link

dtgm commented Jun 24, 2016

@MartiUK sorry about all the confusion. I'm not sure why folks think you are the maintainer of the chocolatey package. The maintainer and software authors are clearly listed separately

To clarify to anyone who may still come across this. The chocolatey package is community driven package that is not affiliated with this project. Currently, the chocolatey package simply downloads the associated zipped file as released from cmderdev/cmder repository and extracts to whatever $env:ChocolateyToolsLocation is set to (if the variable does not exist or is empty, it defaults to C:\tools). It then adds the location to the path.

If anyone has an issue with the chocolatey package, please use the Contact Maintainers as listed alongside the package.

The package gets automatically built whenever a new version is detected from the URL https://github.com/cmderdev/cmder/releases/latest (currently 1.1.4.1)

Pre-release versions are required to be built manually. See the "Package Source" link also listed alongside the package for contributing. You must also pass --prerelease option when installing or only the latest stable version will install, since packages marked --prerelease are exempt from moderation.

@jankatins
Copy link
Contributor

@dtgm:

The package gets automatically built whenever a new version is detected from the URL https://github.com/cmderdev/cmder/releases/latest (currently 1.1.4.1)

Do you have a pointer to the script which does this? I'm curious and have a use case in conda-forge for it :-)

@dtgm
Copy link

dtgm commented Jun 24, 2016

@JanSchulz Yup, the package source files are all in my repo including the auto-updating routines. The relevant file is https://github.com/dtgm/chocolatey-packages/blob/master/ketarin/cmder.xml You can see the regex I'm using in that file to scrape the page for the relevant file and extract the version. Also grab the MD5 from GitHub. You can either use the relevant bits of the XML in another program or load it into ketarin (GPLv2). There are some other bits that do the actual building of the nupkg.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants