search

adorepump / chocolatey-packages

a list of packages i've been making for site chocolatey.org
3 stars 17 forks source link

In regard to the vagrant package... #12

Open webcoyote opened 11 years ago

webcoyote commented 11 years ago

Hello,

I've been using chocolatey to install vagrant and created my own chocolatey package called vagrant-base, probably for the same reason you created vagrant.install -- because vagrant was out-of-date.

I asked Rob Reynolds (FerventCoder on Chocolatey) if he was going to update the vagrant package and instead he asked me to be the maintainer. I have updated it to version 1.0.6 of Vagrant, removed unnecessary dependencies (putty & jruby) and allow the user to set the install location using the chocolatey bin directory.

I wondered if there were any other changes that you wanted to include in the vagrant project, and discover whether there was a way to combine the two projects to avoid confusion.

If you'd like to make any changes, I have a small repo at https://github.com/webcoyote/chocolatey-packages.

Best,

Pat

adorepump commented 11 years ago

hello patrick, I use ruby and vagrant sometimes, after many tries to install vagrant in windows7 machine/64bits, the only way to works, was the install the .exe/msi of the vagrant.

installing a version of jruby/gem install vagrant, in windows, for my

experience it not works.

there's other chocolatey package i made that is out-to-date, for me, the most difficult part is to update the version frequently, and I dont have time/habit to see if there is a version of the program.

to ssh the virtual machine, its recommended to use a ssh client, like putty, the cmd> vagrant ssh does not works at windows.

for this reason I put putty(chocolatey package) as dependencies.

At chocolatey project, its not a good idea to have 2/more packages doing the same thing, Sometimes this situation happens at chocolatey/wiki, its best solution is to merge the solutions. we need to see if this is solution we'll adopt.

Thanks for helping. Elliando Dias

2013/2/15 Patrick Wyatt notifications@github.com

Hello,

I've been using chocolatey to install vagrant and created my own chocolatey package called vagrant-basehttp://chocolatey.org/packages/vagrant-base, probably for the same reason you created vagrant.installhttp://chocolatey.org/packages/Vagrant.install-- because vagrant http://chocolatey.org/packages/vagrant was out-of-date.

I asked Rob Reynolds (FerventCoder on Chocolatey) if he was going to update the vagrant package and instead he asked me to be the maintainer. I have updated it to version 1.0.6 of Vagrant, removed unnecessary dependencies (putty & jruby) and allow the user to set the install location using the chocolatey bin directory.

I wondered if there were any other changes that you wanted to include in the vagrant project, and discover whether there was a way to combine the two projects to avoid confusion.

If you'd like to make any changes, I have a small repo at https://github.com/webcoyote/chocolatey-packages.

Best,

Pat

— Reply to this email directly or view it on GitHubhttps://github.com/adorepump/chocolatey-packages/issues/12.

Abraços Elliando Dias;

webcoyote commented 11 years ago

Hello Elliando,

I agree, the MSI installer for Vagrant makes things work better; because Vagrant now comes pre-bundled with its own embedded version of Ruby there are no incompatibility issues.

If you don't have time to update your chocolatey package, may I suggest "unlisting" it? On your administration page you can click the "listed - yes" to change it to "listed - no" so that it won't get found in the search panel, which will reduce the confusion for other users. I'll endeavor to keep my version of the package updated. I'm going to look into automating the update process to ensure that it stays up to date!

In regard to SSH, I used to use Putty but discovered that many packages on Windows now ship with an SSH command-line client, including Git and msys/MinGW. Consequently, rather than including Putty as a dependency, I let users choose which they would prefer: Putty or SSH.

Further, it was the case that "vagrant ssh" did not work on Windows, but it should start working in version 1.10. I submitted this pull requesthttps://github.com/mitchellh/vagrant/pull/933which was incorporated by Mitchell, and as soon as he releases the next version things should be great. In the meantime you can also call SSH directly, which I put into a batch file for convenience:

https://github.com/webcoyote/linux-vm/blob/master/operator-ssh.bat

In my case I use the ssh.exe which is installed to:

C:>where ssh C:\Program Files (x86)\Git\bin\ssh.exe

Again, if there's anything else please let me know or submit a pull request to my repository and I'll check it out right away!

Best,

Pat

On Sat, Feb 16, 2013 at 11:43 AM, Elliando Dias notifications@github.comwrote:

hello patrick, I use ruby and vagrant sometimes, after many tries to install vagrant in windows7 machine/64bits, the only way to works, was the install the .exe/msi of the vagrant.

installing a version of jruby/gem install vagrant, in windows, for my

experience it not works.

there's other chocolatey package i made that is out-to-date, for me, the most difficult part is to update the version frequently, and I dont have time/habit to see if there is a version of the program.

to ssh the virtual machine, its recommended to use a ssh client, like putty, the cmd> vagrant ssh does not works at windows.

for this reason I put putty(chocolatey package) as dependencies.

At chocolatey project, its not a good idea to have 2/more packages doing the same thing, Sometimes this situation happens at chocolatey/wiki, its best solution is to merge the solutions. we need to see if this is solution we'll adopt.

Thanks for helping. Elliando Dias

2013/2/15 Patrick Wyatt notifications@github.com

Hello,

I've been using chocolatey to install vagrant and created my own chocolatey package called vagrant-base< http://chocolatey.org/packages/vagrant-base>, probably for the same reason you created vagrant.install< http://chocolatey.org/packages/Vagrant.install>-- because vagrant http://chocolatey.org/packages/vagrant was out-of-date.

I asked Rob Reynolds (FerventCoder on Chocolatey) if he was going to update the vagrant package and instead he asked me to be the maintainer. I have updated it to version 1.0.6 of Vagrant, removed unnecessary dependencies (putty & jruby) and allow the user to set the install location using the chocolatey bin directory.

I wondered if there were any other changes that you wanted to include in the vagrant project, and discover whether there was a way to combine the two projects to avoid confusion.

If you'd like to make any changes, I have a small repo at https://github.com/webcoyote/chocolatey-packages.

Best,

Pat

— Reply to this email directly or view it on GitHub< https://github.com/adorepump/chocolatey-packages/issues/12>.

Abraços Elliando Dias;

— Reply to this email directly or view it on GitHubhttps://github.com/adorepump/chocolatey-packages/issues/12#issuecomment-13670793.