> On Jun 2, 2016, at 2:52 AM, Tomas Hrcka <[email protected]> wrote:
>
>
>
>> On 06/01/2016 03:59 PM, Stephen Gallagher wrote:
>>> On 06/01/2016 08:25 AM, Tomas Hrcka wrote:
>>> Hi,
>>>
>>> I was responsible for nodejs in rhscl but my day job has changed.
>>>
>>> But I do have interest in having latest stable releases of nodejs working
>>> on fedora.
>>>
>>> I can dedicate to this work 2-4 hours per week. Now when we are shipping
>>> bundled
>>> npm and some other deps.
>>>
>>> it may be doable for me.
>>>
>> At this point, I *think* I've gotten the spec file in good enough shape that
>> updating to newer versions of Node.js should be fairly straightforward. (I'll
>> remind people however that we've decided that Fedora will always ship the
>> latest
>> LTS release of Node.js in the official repositories and maintain that same
>> version for that Fedora release.)
>
> I was watching work you have done on nodejs,
> and as you mentioned spec file seems to be in good shape thanks for that.
> Do you really mean LTS release? Because current LTS is 4.2 but stable is 6.2.
> I am in contact with multiple consumers of nodejs and current stable release
> may be better choice for fedora. Another option is to have LTS in current
> fedora release and latest stable in rawhide.
> Stable releases are much more useful in context of fedora since its used
> mostly by devels and we have LTS in centos as scl.
>
> I am volunteering in both cases.
>
I meant "the release that will be LTS". Looking at the release cycle, that
sounds like basically each of the even-numbered releases. Having the
odd-numbered ones in Rawhide is problematic, as we saw this time around, since
they only have nine months of support.
The odd-numbered ones could go to a COPR, though.
>>
>> The steps to update Node.js should be as follows (We should probably write
>> this
>> into a wiki page somewhere...)
>>
>>
>> 1. Modify nodejs.spec and set the nodejs_{major|minor|patch} versions to the
>> new
>> release. Save it.
>> 2. Run ./nodejs-tarball.sh
>> 3. Run `fedpkg new-sources nodejs-vM-m-p-stripped.tar.gz`
>> Note: do *not* commit the unstripped tarball; it contains a bundled
>> version
>> of OpenSSL containing encryption algorithms of uncertain legal status. Fedora
>> cannot include them in the SRPM.
>> 4. Run `fedpkg prep` and examine the versions of the bundled c-ares,
>> http_parser, punycode and npm. Update the spec file with any version changes.
>> (The spec file contains comments directing you to the path to where you can
>> find
>> the versions).
>> 4.a. If `fedpkg prep` fails to apply the patches, you will probably need to
>> modify them. The most troublesome one is the one to use the system
>> certificate
>> store. You may be able to coordinate with Joseph Wang <[email protected]> on
>> this if you need help.
>> 5. Run a test build (I usually unset %{with_debug} for this, so it takes half
>> the time).
>> 6. Push and build in the appropriate Fedora branches.
>> _______________________________________________
>> nodejs mailing list
>> [email protected]
>> https://lists.fedoraproject.org/admin/lists/[email protected]
> _______________________________________________
> nodejs mailing list
> [email protected]
> https://lists.fedoraproject.org/admin/lists/[email protected]
_______________________________________________
nodejs mailing list
[email protected]
https://lists.fedoraproject.org/admin/lists/[email protected]
