-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 01/15/2016 09:22 AM, Jared K. Smith wrote:
On Thu, Jan 14, 2016 at 4:04 PM, Tom Hughes <tom(a)compton.nu
<mailto:tom@compton.nu>> wrote:
This specific issue will stop being a problem when node 4 is
merged anyway as I understand it, as that has PPC support?
That's my understanding.
Incidentally, is there a good reason why we don't merge the side
tag given that all the binary issues are sorted and we seem to be
doing the npm stack in the main tag anyway?
Good question -- I knew that we were doing all the npm
*dependencies* in the main tag in rawhide, but I didn't know if we
needed to do npm itself in the side tag. Without really thinking
about it too hard this morning, I can't think of a reason not to
merge the side tag.
The reason for the side-tag was to deal with rebuilds for packages
that were not compatible with both 0.10.x and 4.x. That seems to have
failed anyway, since we have nodejs-got in Rawhide requiring 4.x+
The remaining problem is still npm *itself*, since I'm not certain if
the current version of npm in Rawhide will work with 4.x, so I'd
prefer not to merge until we get that built.
I'm working on the last couple packages today, so I suspect we'll be
ready to build npm very soon.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iEYEARECAAYFAlaZAawACgkQeiVVYja6o6PvMACfTvcu3xjDUMbcGr7W7C8Jy4ct
q0MAn3lDFjVGZPdTusE0tSZBgKnycfWb
=oLHt
-----END PGP SIGNATURE-----