nodejs July 2013

nodejs@lists.fedoraproject.org

6 participants
10 discussions

[fpc] #311: Node.js guidelines update
by fedora-badges 08 Mar '14

08 Mar '14

#311: Node.js guidelines update -----------------------------+------------------ Reporter: patches | Owner: Type: enhancement | Status: new Priority: minor | Milestone: Component: Guideline Draft | Version: Keywords: | Blocked By: Blocking: | -----------------------------+------------------ We have a couple of changes we'd like to make to the Node.js Guidelines after several months of refining our processes a little bit. You can see the new draft at: https://fedoraproject.org/wiki/User:Patches/PackagingDrafts/NodeJS The changes include: * I've restored the %nodejs_fixdep section included in the original version of the draft. After reviewing the IRC logs, it seemed FPC didn't strongly object to this, and I believe it has several advantages to patch- based workflows. Not only is it simpler for packagers, but it also makes them dead simple to audit later on for staleness/compliance/whathaveyou. (`grep -r nodejs_fixdep` is just a lot easier than trying to find relevant patches. ;-) It also makes changes to dependencies much easier to see in git. [https://fedoraproject.org/wiki/User:Patches/PackagingDrafts/NodeJS#Correcti… (relevant section)] [https://fedoraproject.org/w/index.php?title=User:Patches/PackagingDrafts/No… (diff)] * The RPM magic was recently split into it's own "nodejs-packaging" SRPM, similar to Java. Accordingly, packages can now require "nodejs-packaging" instead of "nodejs-devel" to reduce the number of deps dragged in at build-time. [https://fedoraproject.org/wiki/User:Patches/PackagingDrafts/NodeJS#BuildReq… (relevant section)] [https://fedoraproject.org/w/index.php?title=User:Patches/PackagingDrafts/No… (diff #1)] [https://fedoraproject.org/w/index.php?title=User:Patches/PackagingDrafts/No… (diff #2)] [https://lists.fedoraproject.org/pipermail/nodejs/2013-April/000001.html (list discussion)] * The necessary ExclusiveArch line needed for Node.js packages is now documented, including the %{nodejs_arches} macro recently added to redhat- rpm-config for this purpose. [https://fedoraproject.org/wiki/User:Patches/PackagingDrafts/NodeJS#Exclusiv… (new section)] [https://lists.fedoraproject.org/pipermail/nodejs/2013-May/000017.html (list discussion)] * A strategy for handling multiple/compatibility versions of packages that is transparent to dependent packagers has been implemented. [https://fedoraproject.org/wiki/User:Patches/PackagingDrafts/NodeJS#Handling… (new section)] [https://lists.fedoraproject.org/pipermail/nodejs/2013-June/000032.html (list discussion)] * The %{nodejs_default_filter} default automatic virtual provides filtering macro (similar to Perl's) is now documented. [https://fedoraproject.org/wiki/User:Patches/PackagingDrafts/NodeJS#Filterin… (new section)] * A --check argument was added to %nodejs_symlink_deps simplify running test suites in specs. [https://fedoraproject.org/wiki/User:Patches/PackagingDrafts/NodeJS#.25check (new section)] * A brief mention that additional virtual provides are added for native modules to track ABI compatibility was added. [https://fedoraproject.org/w/index.php?title=User:Patches/PackagingDrafts/No… (diff)] * Some minor edits were made to the installing native modules section to reflect reality; my initial draft contained errors. [https://fedoraproject.org/w/index.php?title=User:Patches/PackagingDrafts/No… (diff)] * A brief note about an additional macro required to enable dependency generation on EPEL was added. [https://fedoraproject.org/w/index.php?title=User:Patches/PackagingDrafts/No… (diff)] I'd like to thank the fledgling Node.js SIG, including Stephen Gallager, Jamie Nguyen, Tom Hughes, and Stanislav Ochotnicky for their valuable bug catching, feedback, and suggestions, without which none of this would be possible. And, also the FPC in advance for reviewing our changes, of course. ;-) -- Ticket URL: <https://fedorahosted.org/fpc/ticket/311> fpc <https://fedoraproject.org/wiki/Packaging:Committee> Fedora Packages Collection Task Tracking

3 6

[HEADSUP] npm in EPEL broken due to rel-eng issue
by T.C. Hollingsworth 04 Jan '14

04 Jan '14

npm currently has broken dependencies in EPEL 6 because of what appears to be a rel-eng issue: https://fedorahosted.org/rel-eng/ticket/5657 Ordinarily I'd unpush that update but I'd rather wait for rel-eng's advice since something strange seems to have gone wrong here. -T.C.

3 7

npm license change
by T.C. Hollingsworth 30 Jul '13

30 Jul '13

npm, the Node.js package manager, has changed license [1] from a modified version of the MIT [2] to the Artistic 2.0 [3] license effective with version 1.3.6. This version is now in Rawhide and queued for updates-testing in Fedora 19 and 18 as well as EPEL 6. Fedora Legal believes both licenses to be GPL-compatible so this shouldn't cause anyone trouble. On the contrary, using a standard license instead of a custom-written one should only make peoples' lives easier. ;-) -T.C. [1] https://github.com/isaacs/npm/commit/c32391b1efd70a861cebc77e0cc784a46af5de… [2] https://fedoraproject.org/wiki/Licensing/MITNFA [3] http://www.perlfoundation.org/artistic_license_2_0

1 0

nodejs-symlink-deps fails when module is listed in deps and devdeps
by Jamie Nguyen 30 Jul '13

30 Jul '13

Hi, Came across an issue with nodejs-snockets which lists coffee-script in package.json in both a 'dependencies' and 'devDependencies'. Creating the second symlink fails with 'OSError file exists'. Pull request sent: https://github.com/tchollingsworth/nodejs-packaging/pull/1 Kind regards, -- Jamie Nguyen

2 2

Broken dependencies in rawhide
by Tom Hughes 15 Jul '13

15 Jul '13

There seems to be a broken dependency in rawhide that is, among other things, making it impossible to build any binary node packages: Error: Package: nodejs-fstream-0.1.22-3.fc20.noarch (@fedora-rawhide) Requires: npm(graceful-fs) < 1.3 Removing: nodejs-graceful-fs-1.2.2-1.fc20.noarch (@fedora-rawhide) npm(graceful-fs) = 1.2.2 Updated By: nodejs-graceful-fs-2.0.0-2.fc20.noarch (fedora-rawhide) npm(graceful-fs) = 2.0.0 Tom -- Tom Hughes (tom(a)compton.nu) http://compton.nu/

2 2

EL6 going crazy again
by Jamie Nguyen 13 Jul '13

13 Jul '13

Hi, I've had a re-occurrence of this bug, where the npm(foo) Provides and Requires are all missing: https://bugzilla.redhat.com/show_bug.cgi?id=968776 Build of nodejs-i2c on F19 looks fine: http://koji.fedoraproject.org/koji/rpminfo?rpmID=4135804 Build of nodejs-i2c on EL6 missing all of the 'npm(foo)' Provides and Requires: http://koji.fedoraproject.org/koji/rpminfo?rpmID=4135799 Similarly, nodejs-repl on F19 looks fine: http://koji.fedoraproject.org/koji/rpminfo?rpmID=4099064 nodejs-repl on EL6 missing Provides npm(repl): http://koji.fedoraproject.org/koji/rpminfo?rpmID=4099077 Presumably the cause is the same, and I'll just rebuild them to fix, but did we ever figure out exactly what's happening? Kind regards, -- Jamie Nguyen

2 3

Request for karma to fix broken deps on f19
by Jamie Nguyen 12 Jul '13

12 Jul '13

Hi! Would really appreciate if a couple of you gave some karma for these two updates: https://admin.fedoraproject.org/updates/FEDORA-2013-12470/nodejs-tap-0.4.1-… https://admin.fedoraproject.org/updates/FEDORA-2013-12446/nodejs-vows-0.7.0… Broken deps on F19 not so cool :( -- Jamie Nguyen

3 4

JavaScript guidelines
by T.C. Hollingsworth 10 Jul '13

10 Jul '13

Hi Fedora Noders! I've mentioned the imminence of this in several bugs with several of you, and now the time has come! Please join us over on the packaging list for what is sure to be a lively discussion about some bona fide JavaScript guidelines for the distribution: https://lists.fedoraproject.org/pipermail/packaging/2013-July/009304.html Thanks! -T.C.

1 0

Packaging puzzle
by Tom Hughes 04 Jul '13

04 Jul '13

I'm trying to package the mapnik module, but the latest version has a dependency on the mapnik-vector-tile module, which turns out to be a rather odd beast... Basically mapnik-vector-tile has a src directory, containing some .hpp files, and a proto directory with a protobuf definition file. When make is run the protobuf definition is compiled to a .h and .cc pair in the src directory. That is it - no compiled code, no javascript, so it's not actually loadable by node in any way. What then happens is that the mapnik module pulls in the cpp file as part of the so it builds - the binding.gyp in mapnik actually includes node_modules/mapnik-vector-tile/src/vector_tile.pb.cc in it's source file list. Any suggestions on how to package this? Should I just package the dependent module and have it install the src directory so that the mapnik module can use it when building? Tom -- Tom Hughes (tom(a)compton.nu) http://compton.nu/

2 1

Fwd: [ANN] Fedora 19 - now with 100% more node
by T.C. Hollingsworth 02 Jul '13

02 Jul '13

Thanks to everyone who helped make this possible! https://groups.google.com/forum/#!topic/nodejs/mTz1MT_seMk ---------- Forwarded message ---------- From: T.C. Hollingsworth <tchollingsworth(a)gmail.com> Date: Tue, Jul 2, 2013 at 8:40 AM Subject: [ANN] Fedora 19 - now with 100% more node To: nodejs(a)googlegroups.com The Fedora Node.js Special Interest Group is delighted to announce the release of Fedora 19 ("Schrödinger's Cat"), the first Fedora release to include node right from the start. Open the box and take a look for yourself! What's Fedora? Fedora is a leading-edge, free and open source operating system that continues to deliver innovative features to many users, with a new release about every six months. Download it now! Or, learn more about Fedora. What does this mean? Installing node and npm at the same time is now as easy as: sudo yum install npm That's it! No more compiling—you get the latest node just like you're used to getting the latest everything. And yes, we support Fedora 18 and EPEL 6 too. Not to mention Pidora on your Raspberry Pi and all kinds of other fun ARM systems. What about those pesky native modules? Don't I still need a compiler for them? Not for a select number of modules (which we hope to grow here very soon). If one you need happens to be one of the lucky few, install it with yum and then npm link it into your project, like this example with libxmljs: sudo yum install 'npm(libxmljs)' cd /path/to/my/awesome/project npm link libxmljs Of course, npm install will always work, if we don't the module you're looking for or you want to look fondly back upon the old days. Can I help make that number less "select"? You sure can. We can always use a little more help! What else in Fedora 19 might interest me? Developer's Assistant is a tool for new developers that helps you to get started on a code project by offering templates, samples, and toolchains for a variety of languages. And when you're finished, you can publish directly to GitHub! 3D modelling and printing are supported with OpenSCAD, Skeinforge, SFACT, Printrun, RepetierHost, and other tool options. OpenShift Origin makes it easy for you to build your own Platform-as-a-Service (PaaS) infrastructure, allowing you to enable others to easily develop and deploy software. And of course it supports node, just like its cloudy counterpart. MariaDB offers a truly open MySQL implementation and is now the default MySQL option in Fedora. systemd Resource Control is one of many systemd enhancements in this release. It lets you modify your service settings without a reboot by dynamically querying and modifying resource control parameters at runtime. GCC 4.8 contains the latest compiler optimizations—for when JavaScript isn't enough. And much, much more! You didn't answer my question! Feel free to reply here. You can also ask Fedora-specific node-related questions over at nodejs at lists.fedoraproject.org. What are you waiting for? Go get it now, and enjoy!

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

nodejs July 2013