Gem version? about fakefs

[defunkt]

I rolled a gem and pushed it to http://gemcutter.org/

gem install fakefs should work now.

[adamsalter]

Yep...

Well gem install gemcutter, gem tumble, gem install fakefs

If I put gemcutter as a dependency they will still have to gem tumble at least once... I'll put it in the docs and hope...

I'm in a similar position where I'm not sure I can be bothered with the whole rubyforge lifecycle just to publish a gem (although they do accept git repos now, so it shouldn't be too hard to set up).

Cheers for the quick setup ;)

[defunkt]

It shouldn't be that big of a problem if it's a development time dependency, right?

[adamsalter]

Yeah, sure. It's not huge priority. I guess I'm not really sure what would happen if somebody tried to install my gem with fakefs and gemcutter as dependencies... as I'm guessing you know gems have 'dependencies' and 'development_dependencies' but either way the user isn't going to be able install fakefs as normal, unless they have already used gemcutter previously and I'll have to document it, just in case.

It's probably complicated by the fact fakefs is a dependency (ie other gems will depend on it to function)... if you just wanted to install it for normal use then you could specify gemcutter as the source and gem install fakefs --source=http://gemcutter.org.

I'd like to note that I'm not pushing for a rubyforge release. I'm happy with this solution. I've also put my gem on gemcutter over rubyforge... It's more a limitation with the current gemcutter install (maybe - since I haven't fully tested it yet).

Actually... come to think of it... If I release my gem on gemcutter then it's problem solved... I'm also going to do a little testing with the github gem... maybe it will 'just work' (tm) (although it definitely failed when done manually).