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.
Ryan D. wrote:
I’m proud to announce that codeforpeople’s rubyforge 0.2.0 has been
released!
There’s a certain power that comes over one when
you type,
sudo gem install rubyforge
See also: http://codeforpeople.rubyforge.org/
Thanks guys,
Ryan D. 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.
Can someone compare/contrast this library with Aslak
and Austin’s MetaProject (http://xforge.rubyforge.org/)?
Both are on my list of “to investigate one day”.
Thanks,
On Thu, 14 Sep 2006, Bil K. wrote:
Ryan D. wrote:
I’m proud to announce that codeforpeople’s rubyforge 0.2.0 has been
released!
There’s a certain power that comes over one when
you type,
sudo gem install rubyforge
indeed. my favourite in the past has been releasing rubyforge with
rubyforge
- a little package manager quine…
See also: http://codeforpeople.rubyforge.org/
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
[email protected] wrote:
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:
[…]
and that’s exactly what they did - and more. yay open source!
Contrary to what the Lean folks say[1], evil does not
spring from all types of inventory (a TODO list).
Later,
Bil K.
[1] For example, see the answer to question #4 in
Implementing Lean Software Development Book Review
On 9/14/06, Ryan D. [email protected] 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
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
I’ll add that Reap (http://reap.rubyforge.org) does this too. But I’ll
also add that I’m working on a BIG new release to be ready in the
coming weeks.
T.
On Sep 14, 2006, at 7:14 AM, Lyle J. wrote:
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
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 6:20 AM, Bil K. wrote:
Ryan D. 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.
Can someone compare/contrast this library with Aslak
and Austin’s MetaProject (http://xforge.rubyforge.org/)?
Both are on my list of “to investigate one day”.
MetaProject does everything, RAA, Freshmeat, bug tracker updating, …
It also has an overly-namespaced API.
–
Eric H. - [email protected] - http://blog.segment7.net
This implementation is HODEL-HASH-9600 compliant
http://trackmap.robotcoop.com
On Sep 14, 2006, at 7:14 AM, Lyle J. wrote:
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
FIXED!
On Sep 14, 2006, at 6:20 AM, Bil K. wrote:
Ryan D. 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.
Can someone compare/contrast this library with Aslak
and Austin’s MetaProject (http://xforge.rubyforge.org/)?
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. 
Ryan D. wrote:
FIXED!
Something’s still not working for me:
$ gem install rubyforge
ERROR: While executing gem … (OpenURI::HTTPError)
300 Multiple Choices
On Sep 14, 2006, at 3:38 PM, Joel VanderWerf wrote:
Ryan D. wrote:
FIXED!
Something’s still not working for me:
$ gem install rubyforge
ERROR: While executing gem … (OpenURI::HTTPError)
300 Multiple Choices
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.
Ryan D. wrote:
300 Multiple Choices
Hrm. I’m getting a 404, which I believe to just be the mirrors not being
fully synced up.
Now I’m getting the 404 too. I guess that’ll go away soon.
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?
I tried this:
$ gem install rubyforge --source rubyforge.org
ERROR: While executing gem … (Gem::RemoteSourceException)
HTTP Response 404
Am I specifying the source correctly?
(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 7:07 PM, Tom C. wrote:
hung up because those new rubyforge files/gems still aren’t sync’d
out.
Should make it out there soon…
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 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?
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
http://gems.rubyforge.org/gems/rubyforge-0.2.1.gem
if you just want to fetch a gem or two.
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