Add gemspecs

[xxx]

It would be great to be able to use remarkable with Rails 3.1 without deprecation warnings, but there's no way to do that right now without forking the gem, due to lack of gemspecs. Either adding gemspecs, or releasing a new version of the gem would resolve this.

[Edit by Hosh: Moved Rails 3.1 without deprecation to a different issue #32]

[hosh]

These are two separate issues. Someone has asked for gemspecs ... and now that I've worked with using git submodule without them, it's enough of an itch that I'll go ahead and do that.

Rails 3.1 without deprecation warning is in the works in the Rails 3.1 branch.

[xxx]

ack, yeah I'm using the 3.1 branch, but had to fork because I can't point a Gemfile at a repo that doesn't have gemspecs, or alternately use a released gem that includes the 3.1 fixes. Didn't intend the 3.1 deprecations to be part of this.

[hosh]

@xxx roger.

[bitcoiners]

any progress on the gemspecs?

[dmathieu]

Please, do this. All the rails warnings are getting boring.

[ippy04]

+1

[tigrish]

I'm running into this issue too, trying to upgrade an app to rails 3.2.

[sujoyg]

The lack of a gemspec is preventing us from using this with Rails 3.2. The issues with primary_key_name seems to have been been fixed in master, but an updated gem not released yet. On the other hand, lack of a gemspec file makes it impossible to pull the latest code in the project Gemfile.

[saks]

Can anyone tell me, what is the problem with releasing new version ir adding gemspec?

[xxx]

I ended up forking the repo and adding gemspecs where we needed them. We're using it in 3.2 right now without issue.

[tigrish]

We couldn't wait for progress on this so we ended up migrating our app to shoulda_matchers which provides much of the same functionality.

Too bad, I really liked this project...

On 31 Mar 2012, at 21:39, Michael Dunganreply@reply.github.com wrote:

I ended up forking the repo and adding gemspecs where we needed them. We're using it in 3.2 right now without issue.

---

Reply to this email directly or view it on GitHub:
#36 (comment)

[hosh]

@tigrish shoulda_matchers may be a better fit for most people anyways. I'm not entirely satisfied with the backend but oh well.

[hosh]

@saks Time. I just recently signed up to Opscode so I'll have some free time coming up this week.