On 06/06/14 14:44, Troy Dawson wrote:
But nodejs-nan is making me change my habbit.
Since May 6 (less than 30 days ago), there has been
nan 1.0.0 (which broke the ~0.8 dependencies) nan 1.1.0 (which broke the ~1.0 dependencies) nan 1.1.2 nan 1.2.0 (which broke the ~1.1 dependencies)
Wow!
By "broke" do you just mean that the dependency wasn't met, or do you mean that the dependent packages actually needed code changes to work with the newer version of nan?
I have a few packages that currently depend on ~1.0. In the past they generally updated a few days after nan updated. None of them have this time. I wouldn't be worried if they were doing ^1.0, but they aren't yet.
So is there a reason not to patch them to use ^1.0 with %nodejs_fixdep?
I loosen the requirements in some of my modules which have overly strict requirements on other modules.
Tom