search

rubymotion-community / motion-support

Commonly useful extensions to the standard library for RubyMotion
MIT License
132 stars 28 forks source link

Time for a version bump and gem push? #5

Closed DougPuchalski closed 11 years ago

DougPuchalski commented 11 years ago

I'm noticing things are not up to date in 0.1 rubygem.

tkadauke commented 11 years ago

Working on it … Expect a release soon :-)

DougPuchalski commented 11 years ago

FYI still setting 0.1.0 on http://rubygems.org/gems/motion-support

tkadauke commented 11 years ago

Grr. For some reason Github rejected the tags, so rake release reverted the taggings and didn't push to rubygems.org. I should've checked the output. Thanks for reporting it! Now it's really released :-)

DougPuchalski commented 11 years ago

When building with the entire lib I get

ERROR! Can't resolve dependency `/.../vendor/motion-support/lib/motion-support/_stdlib/cgi.rb'

Have you seen this?

On Monday, April 29, 2013 at 10:30 PM, Thomas Kadauke wrote:

Grr. For some reason Github rejected the tags, so rake release reverted the taggings and didn't push to rubygems.org (http://rubygems.org). I should've checked the output. Thanks for reporting it! Now it's really released :-)

— Reply to this email directly or view it on GitHub (https://github.com/tkadauke/motion-support/issues/5#issuecomment-17210227).

tkadauke commented 11 years ago

Not really.

What exactly do you do to build the lib? Do you run rake within the motion-support directory? Or do you require it from your own project?

If you require it from your app, please make sure that you turn off automatic dependency detection. It does not work with motion-support.

On 30.04.2013, at 16:32, Doug Puchalski notifications@github.com wrote:

When building with the entire lib I get

ERROR! Can't resolve dependency `/.../vendor/motion-support/lib/motion-support/_stdlib/cgi.rb'

Have you seen this?

On Monday, April 29, 2013 at 10:30 PM, Thomas Kadauke wrote:

Grr. For some reason Github rejected the tags, so rake release reverted the taggings and didn't push to rubygems.org (http://rubygems.org). I should've checked the output. Thanks for reporting it! Now it's really released :-)

— Reply to this email directly or view it on GitHub (https://github.com/tkadauke/motion-support/issues/5#issuecomment-17210227).

— Reply to this email directly or view it on GitHub.

DougPuchalski commented 11 years ago

I realize turning off dependency detection may be the easiest solution in isolation, but I think adoption could be limited by the requirement.

On Tuesday, April 30, 2013 at 7:38 AM, Thomas Kadauke wrote:

Not really.

What exactly do you do to build the lib? Do you run rake within the motion-support directory? Or do you require it from your own project?

If you require it from your app, please make sure that you turn off automatic dependency detection. It does not work with motion-support.

On 30.04.2013, at 16:32, Doug Puchalski <notifications@github.com (mailto:notifications@github.com)> wrote:

When building with the entire lib I get

ERROR! Can't resolve dependency `/.../vendor/motion-support/lib/motion-support/_stdlib/cgi.rb'

Have you seen this?

On Monday, April 29, 2013 at 10:30 PM, Thomas Kadauke wrote:

Grr. For some reason Github rejected the tags, so rake release reverted the taggings and didn't push to rubygems.org (http://rubygems.org) (http://rubygems.org). I should've checked the output. Thanks for reporting it! Now it's really released :-)

—
Reply to this email directly or view it on GitHub (https://github.com/tkadauke/motion-support/issues/5#issuecomment-17210227).

—
Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub (https://github.com/tkadauke/motion-support/issues/5#issuecomment-17231012).

tkadauke commented 11 years ago

It is quite well known that automatic dependency detection (ADD) is broken right now. There are several fixes as pull requests and if i'm not mistaken, Watson has already committed some fixes to master. You're of course right, but there is no other option right now. At some size of a project, ADD will stop working. That size was reached in MotionSupport very early on. ADD never worked for TinyMon, or any other of my apps, so I got into the habit of turning it off right away.

We'll have to accept that fact until a fix is released and then I will of course remove that constraint from MotionSupport.

DougPuchalski commented 11 years ago

Actually there are other options, I have solved it another way and am using motion-support in a very large project with dependency detection turned on. That's sort of my point, that this should be an application-level decision. Anyway you did put in the warning rather than bombing out so we're good. I'm not currently seeing the issue that started this thread so we can put it aside.