I'm proud to announce that codeforpeople's rubyforge 0.2.0 has been released! This release marks a massive revamp to rubyforge splitting the previous command-line script into a script and library with unit tests. Makeing the system now able to be used directly from Rakefiles and other deployment scripts!
We've extended the command set and added semi-automatic configuration of groups, projects, and releases. We've also added the ability to add files to a release.
We have a lot of plans for this library. Next on the list is to be able to specify multiple files to release all at once, error checking, and a much more powerful configuration system.
We have a lot of plans for this library. Next on the list is to be able to specify multiple files to release all at once, error checking, and a much more powerful configuration system.
OK, I'm having trouble installing the gem. Probably has nothing to do
with the rubyforge project itself, but at any rate, when I do:
sudo gem install rubyforge
I get this:
Attempting local installation of 'rubyforge'
Local gem file not found: rubyforge*.gem
Attempting remote installation of 'rubyforge'
ERROR: While executing gem ... (Errno::ENOENT)
No such file or directory -
/usr/local/lib/ruby/gems/1.8/gems/rubyforge-0.2.0/bin/CVS
I can see that the gem file has at least been downloaded into my
/usr/local/lib/ruby/gems/1.8/cache directory, so it doesn't seem to be
a network problem or anything like that.
Any advice would be appreciated.
Thanks,
Lyle
···
On 9/14/06, Ryan Davis <ryand-ruby@zenspider.com> wrote:
I'm proud to announce that codeforpeople's rubyforge 0.2.0 has been
released! ...
thanks bil. and thanks ryan and eric. those guys just dropped this new
release in my lap the other night and i really appreciate it! the previous
version had this in the TODO section:
TODO
- scrape rubyforge to auto-configure group_id and package_ids.
- objectify the script. it's procedural butchery attm.
and that's exactly what they did - and more. yay open source!
cheers.
-a
···
On Thu, 14 Sep 2006, Bil Kleb wrote:
--
in order to be effective truth must penetrate like an arrow - and that is
likely to hurt. -- wei wu wei
MetaProject does everything, RAA, Freshmeat, bug tracker updating, ...
It also has an overly-namespaced API.
···
On Sep 14, 2006, at 6:20 AM, Bil Kleb wrote:
Ryan Davis wrote:
We have a lot of plans for this library. Next on the list is to be able to specify multiple files to release all at once, error checking, and a much more powerful configuration system.
HAHA! I knew I should have switched the gem over to a manifest based system! SORRY. I'll get that fixed and released today. ** is EVIL.
···
On Sep 14, 2006, at 7:14 AM, Lyle Johnson wrote:
On 9/14/06, Ryan Davis <ryand-ruby@zenspider.com> wrote:
I'm proud to announce that codeforpeople's rubyforge 0.2.0 has been
released! ...
OK, I'm having trouble installing the gem. Probably has nothing to do
with the rubyforge project itself, but at any rate, when I do:
sudo gem install rubyforge
I get this:
Attempting local installation of 'rubyforge'
Local gem file not found: rubyforge*.gem
Attempting remote installation of 'rubyforge'
ERROR: While executing gem ... (Errno::ENOENT)
No such file or directory -
/usr/local/lib/ruby/gems/1.8/gems/rubyforge-0.2.0/bin/CVS
metaproject is big to the point of obfuscation and intimidation (to me). I wanted to automate deployment. That is it. Ara's code shines with clarity of thought and we glommed onto it immediately. It was relatively tiny, did one thing, and did it rather well. Now it does it better.
···
On Sep 14, 2006, at 6:20 AM, Bil Kleb wrote:
Ryan Davis wrote:
We have a lot of plans for this library. Next on the list is to be able to specify multiple files to release all at once, error checking, and a much more powerful configuration system.
OK, I'm having trouble installing the gem. Probably has nothing to do
with the rubyforge project itself, but at any rate, when I do:
sudo gem install rubyforge
I get this:
Attempting local installation of 'rubyforge'
Local gem file not found: rubyforge*.gem
Attempting remote installation of 'rubyforge'
ERROR: While executing gem ... (Errno::ENOENT)
No such file or directory -
/usr/local/lib/ruby/gems/1.8/gems/rubyforge-0.2.0/bin/CVS
Hrm. I'm getting a 404, which I believe to just be the mirrors not being fully synced up.
As far as the multiple choinces... hrm. I did nuke the release and do it again to test the newer level of deployment automation... so maybe I did that mid sync and they're a bit confused.
···
On Sep 14, 2006, at 3:38 PM, Joel VanderWerf wrote:
(This might not even be a correct workaround, because rubyforge might redirect the request to a mirror anyway, as it does when you click on the links on the download page.)
···
On Sep 14, 2006, at 3:38 PM, Joel VanderWerf wrote:
--
vjoel : Joel VanderWerf : path berkeley edu : 510 665 3407
Actually, RubyForge doesn't serve any gems itself when they're requested
by the RubyGems client app; all those requests get redirected to the
mirrors. Although, really, you just can hit
Anyhow, I'm running a manual file sync now; something must have gotten
hung up because those new rubyforge files/gems still aren't sync'd out.
Should make it out there soon...
Yours,
Tom
···
On Fri, 2006-09-15 at 08:53 +0900, Joel VanderWerf wrote:
Out of curiosity, is there a way to force gem ops to use a particular
repository (in this case, the main rubyforge), to avoid mirroring issues?
Thanks. I tried to find you earlier but you weren't online.
I think the thing was that I released the gem, deleted it about 3-5 minutes later, and released again shortly after that.
···
On Sep 14, 2006, at 7:07 PM, Tom Copeland wrote:
Actually, RubyForge doesn't serve any gems itself when they're requested
by the RubyGems client app; all those requests get redirected to the
mirrors. Although, really, you just can hit
Anyhow, I'm running a manual file sync now; something must have gotten
hung up because those new rubyforge files/gems still aren't sync'd out.
Should make it out there soon...
