I looked at packaging readable-stream a while back. It seemed to provide "stream" fixed at a particular version.
If the packages work with stream in our nodejs package, why bother to change? It is probably easier to use the node-readable-stream package now that it exists for new packages (instead of patching). On 12/06/17 10:15, Paolo Greppi wrote: > Il 12/06/2017 10:00, Debian FTP Masters ha scritto: >> Accepted: >> >> Format: 1.8 >> Date: Sat, 27 May 2017 23:15:41 +0200 >> Source: node-readable-stream >> Binary: node-readable-stream >> Architecture: source all >> Version: 2.2.9-1 >> Distribution: unstable >> Urgency: low >> Maintainer: Debian Javascript Maintainers >> <[email protected]> >> Changed-By: Bastien Roucariès <[email protected]> >> Description: >> node-readable-stream - stream compatibility library for Node.js and browser >> Closes: 863510 >> ... > Many modules have been patched to use nodejs' stream rather than > readable-stream or to skip tests that require readable-stream. > > Now that this is in the archive, should we pick it up ? > > The involved modules (https://codesearch.debian.net/search?q=readable-stream) > are 34: > > node-are-we-there-yet > node-bl > node-cloneable-readable > node-concat-stream > node-duplexer2 > node-duplexify > node-finalhandler > node-first-chunk-stream > node-from2 > node-htmlparser2 > node-isstream > nodejs > node-lazystream > node-lodash > node-log4js > node-memory-fs > node-merge-stream > node-mysql > node-nan > node-ordered-read-streams > node-raw-body > node-sha > node-static-module > node-stream-array > node-streamtest > node-superagent > node-tap > node-tap-parser > node-tar-pack > node-tar-stream > node-through2 > node-unpipe > node-vinyl-fs > node-ytdl-core > > P. > -- Pkg-javascript-devel mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
