Skip to content
This repository has been archived by the owner on Apr 12, 2022. It is now read-only.

Broken gemspec #22

Closed
mootpointer opened this issue Mar 29, 2012 · 1 comment
Closed

Broken gemspec #22

mootpointer opened this issue Mar 29, 2012 · 1 comment

Comments

@mootpointer
Copy link

I've noticed a couple of issues with the gemspec. The first is that soulmate depends on itself. That means that presently I cannot install soulmate using gem install soulmate. Also, jeweler is adding a lot of duplicate dependencies (in fact it adds them every time you run rake gemspec:generate.

I'm not sure what's gone on with the gemspec, but there's obviously some broken stuff there.

@erwaller
Copy link
Member

Sorry about that, and thanks for pointing it out. I'm still figuring out this whole gem packaging thing..

hhkim pushed a commit to hhkim/soulmate that referenced this issue Apr 23, 2012
* upstream/master:
  Regenerate gemspec for version 0.1.3
  v0.1.3
  closes seatgeek#22
  Regenerate gemspec for version 0.1.2
  up version
  Cleanup gemspec/gemfile
  simplify dependencies
  eliminate a warning when running tests (by killing rdoc)
  killed rcov (apparently it doesn't work on 1.9)
  remove Gemfile.lock from git
  reading REDIS_URL from ENV to support solumate on heroku
  updating json dependency in gemspec
  reading connection string from ENV[REDISTOGO_URL] to support solumate on heroku

Conflicts:
	Gemfile
	Gemfile.lock
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants