> On Jun 12, 2016, at 9:23 AM, Robert Van Voorhees <[email protected]> wrote: > > Hi Stephen, > > As per your directions below -- for those that are truly new to the game: > > Where do we checkout the current spec file? (and then push to) -- COPR and > other stuff seem to generate a lot of git repositories along the way. > > In step 6, when you push the updated spec file, does that build it for the > various Fedora branches? > > Sorry if these seem like Fedora packaging 101, just noticed nobody has > responded to this E-mail chain yet. >
A wealth of information on this subject can be found here: https://fedoraproject.org/wiki/Join_the_package_collection_maintainers If you want some personal mentoring, look for me (sgallagh) in #fedora-devel on Freenode IRC and I'll help you get up to speed. >> On Wed, Jun 1, 2016 at 10:01 AM Stephen Gallagher <[email protected]> >> 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.) >> >> 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]
