Hi All, For rawhide I've been trying to keep my nodejs packages up to the latest releases as much as possible. This isn't really that hard because of the wonderful rpm macro's, and the general consistency of npm packages.
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!
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.
Anyway, my plan is to wait until at least one of my packages that depend on nan updates to be able to use the latest nan versions. Then I'll update nan to whatever version that happens to be that day.
Anyone have any better ideas?
Troy
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
On Fri, Jun 6, 2014 at 7:18 AM, Tom Hughes tom@compton.nu wrote:
So is there a reason not to patch them to use ^1.0 with %nodejs_fixdep?
Yes, please do this if at all possible. It'll make things much easier on you. :-)
Remember that as of the latest nodejs-packaging that just went stable, you can do `%nodejs_fixdep --caret nan` in dependent packages to automatically convert the ~ to a ^. (Thus eliminating the need to manually keep up with the minimum acceptable version.)
Also, let me know if you need provenpackager help with some of the dependents.
-T.C.
On 06/06/2014 06:21 PM, T.C. Hollingsworth wrote:
On Fri, Jun 6, 2014 at 7:18 AM, Tom Hughes tom@compton.nu wrote:
So is there a reason not to patch them to use ^1.0 with %nodejs_fixdep?
Yes, please do this if at all possible. It'll make things much easier on you. :-)
Remember that as of the latest nodejs-packaging that just went stable, you can do `%nodejs_fixdep --caret nan` in dependent packages to automatically convert the ~ to a ^. (Thus eliminating the need to manually keep up with the minimum acceptable version.)
Also, let me know if you need provenpackager help with some of the dependents.
-T.C.
Will do. Though I still think I'm going to only update nodejs-nan once a month unless one of the changes is a security one. Once a week seems excessive even for rawhide. Troy
nodejs@lists.fedoraproject.org
-
T.C. Hollingsworth -
Tom Hughes -
Troy Dawson