On Wed, Jan 9, 2019 at 11:51 AM, Xavier <[email protected]> wrote:
Le 08/01/2019 à 23:23, Jérémy Lal a écrit :
Hi,
is there a reason to keep both
node-duplexer2
node-duplexer3
packages ?
It seems it's feasible to keep only one, unless we miss a deeper
issue ?
Jérémy
Only 1 difference: node-duplexer2 uses `readable-stream` while
node-duplexer3 uses `stream` but there is a debian patch in
node-duplexer2 that replace `readable-stream` by `stream`, so Debian
package are identical (and so have the same RC bug...).
Full diff is attached.
Reverse-dependencies:
* node-duplexer2 :
|
+-> node-multipipe
| |
| +-> node-gulp-util
| |
| +-> gulp & Co
|
+-> node-static-module
| |
| +-> node-brfs
|
+-> node-stream-combiner2
|
+-> node-module-deps
* node-duplexer3 :
|
+-> node-got
|
+-> node-package-json
|
+-> node-latest-version
|
+-> npm
I think we can drop node-duplexer2 and add Provieds: node-duplexer2 to
node-duplexer3. This will also require adding a symlink to duplexer3
from duplexer2 in /usr/lib/nodejs.
--
Pkg-javascript-devel mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
