<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 08/25/2016 08:33 AM, Matthias Runge
wrote:<br>
</div>
<blockquote
cite="mid:c5a669d7-fa16-f23a-b5e4-74302e0449c3@matthias-runge.de"
type="cite">
<pre wrap="">On 25/08/16 13:27, Haïkel wrote:
</pre>
<blockquote type="cite">
<pre wrap="">2016-08-25 8:36 GMT+02:00 Matthias Runge <a class="moz-txt-link-rfc2396E" href="mailto:mrunge@matthias-runge.de"><mrunge@matthias-runge.de></a>:
</pre>
<blockquote type="cite">
<pre wrap="">Hello,
for opstools, we'll need nodejs in a repo, I've seen the Cloud SIG
creating their version, PaaS has done the same (just illustrating, I may
be wrong).
This is mostly a mail to ask for interested persons to join or
coordinate efforts here. No need to do the same work multiple times.
What would be the best repository for cross-SIG dependencies?
Matthias
</pre>
</blockquote>
<pre wrap="">
I'm afraid there is none.
As Cloud SIG needed a lot of common python dependencies, I originally
offered to maintain those in a common
repositories (and why not collaborating with EPEL) but there was
little interest to do so.
We even separated the build tags (hence cloud7-openstack-common-*) to
make the transition easier.
I'm not keen on maintaining separately node.js but the only
alternative we had are SCLs and quite old.
Maybe we could work on a common layer SIG that could serve that role.
Regards,
H.
</pre>
</blockquote>
<pre wrap="">IIRC, EPEL/nodejs-maintainers were looking to upgrade straight to nodejs
version 6.</pre>
</blockquote>
<br>
But not until mid-October, when<br>
". . . the Node.js v6 schedule has it going into LTS mode on the
same day that 0.10.x reaches EOL."<br>
<br>
<blockquote
cite="mid:c5a669d7-fa16-f23a-b5e4-74302e0449c3@matthias-runge.de"
type="cite">
<pre wrap="">
I currently don't know the requirements esp. regarding openssl.</pre>
</blockquote>
<br>
I suppose they have the same patch which allows them to build nodejs
4 (or 6) using openssl 1.0.1<br>
<br>
<blockquote
cite="mid:c5a669d7-fa16-f23a-b5e4-74302e0449c3@matthias-runge.de"
type="cite">
<pre wrap="">
Upstream Nodejs version 6 bundles openssl 1.0.2h, which makes me wonder
if we could simply drop it and link node against the CentOS version of
openssl. We should not maintain another openssl library here.</pre>
</blockquote>
<br>
We'll just use the patch that was discussed previously that allows
us to build nodejs against openssl 1.0.1.<br>
<br>
<blockquote
cite="mid:c5a669d7-fa16-f23a-b5e4-74302e0449c3@matthias-runge.de"
type="cite">
<pre wrap="">
Matthias
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
CentOS-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:CentOS-devel@centos.org">CentOS-devel@centos.org</a>
<a class="moz-txt-link-freetext" href="https://lists.centos.org/mailman/listinfo/centos-devel">https://lists.centos.org/mailman/listinfo/centos-devel</a>
</pre>
</blockquote>
<p><br>
</p>
</body>
</html>