rake rails:freeze:edge on windows
Reported by leethal | April 14th, 2008 @ 08:40 PM
This patch uses the system's 'unzip' command if available, or the rubyzip gem if the system does not have a 'unzip' command (e.g. on windows). If neither is available, it'll ask the user to install the rubyzip gem and exit.
It's rather ugly, though, feel free to improve.
Comments and changes to this ticket
-
leethal April 14th, 2008 @ 08:45 PM
Forgot to mention - this will fail now, as the rails_edge.zip on dev.rubyonrails.org is just an empty file. I tested this with a working zip, the parts except from the invalid zip seems to be working.
-
leethal April 16th, 2008 @ 12:56 PM
- → Title changed from “rake rails:freeze:edge on windows” to “[PATCH] rake rails:freeze:edge on windows”
Should I bump? ; )
-
John Barnette April 22nd, 2008 @ 08:25 AM
- → Title changed from “[PATCH] rake rails:freeze:edge on windows” to “rake rails:freeze:edge on windows”
-
Michael Koziarski April 23rd, 2008 @ 09:31 AM
We're looking into the zip file, it appears to be cron jobs stomping on one another or something.
As for this, perhaps we could extract this all into a class in railties somewhere so the rake task isn't full of this code? Rails::Unzipper or some such?
Look in the 1.2.x branch for a less 'horrible' way to detect whether or not we have a command installed. We used it previously for detecting svn.
-
DHH April 29th, 2008 @ 11:21 PM
- → State changed from “new” to “incomplete”
Change ticket status to open when fixed.
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Source available from github
The Git repository resides at http://github.com/rails
Check out the current development trunk (Edge Rails) with:
git clone git://github.com/rails/rails.git
Creating or reviewing a patch
See the contributor guide.
Creating a feature request
Please don't. If you want a new feature in Rails, you'll have to pull up your sleeves and get busy yourself. Or convince someone else to do it. See the contributor guide on how to get going. But posting them here is just going to lead to ticket root.
Creating a bug report
When creating a bug report, be sure to include as much relevant information as possible. Post the code sample that causes the problem. Preferably, alter the unit tests and show through either changed or added tests how the expected behavior is not occuring.
Security vulnerabilities should be reported via an email to security@rubyonrails.org, do not use trac for reporting security vulnerabilities. All content in trac is publicly available as soon as it is posted.
Then don't get your hopes up. Unless you have a "Code Red, Mission Critical, The World is Coming to an End" kinda bug, you're creating this ticket in the hope that others with the same problem will be able to collaborate with you on solving it. Do not expect that the ticket automatically will see any activity or that others will jump to fix it. Creating a ticket like this is mostly to help yourself start on the path of fixing the problem and for others to sign on to with a "I'm having this problem too".
Tom Ward
Jeff Cohen
iGEL