reference
would be to completely remove those clauses from the policies, but at
the very least, the node and JavaScript policies should be made
consistent.
--
Hubert Chathi <uho...@debian.org> -- https://www.uhoreg.ca/
Jabber: hub...@uhoreg.ca -- Matrix: @uhoreg:matrix.org
PGP/GnuPG key: 40
On Tue, 19 Sep 2017 22:27:34 +0200, Paul Gevers <elb...@debian.org> said:
> Hi Hubert, Thanks for writing this down.
> On 19-09-17 17:58, Hubert Chathi wrote:
>> https://wiki.debian.org/HubertChathi/JavaScriptPolicy
>>
>> Please let me know what you all think of i
On Sat, 19 Aug 2017 12:32:39 +0200, Mathias Behrle <mbeh...@debian.org> said:
> * Hubert Chathi: " [Pkg-javascript-devel] parallel installation" (Mon,
> 14 Aug 2017 14:38:34 -0400):
> I appreciate very much the initiative to find a common procedure for
> making d
now that several DDs have had to
educate their upstreams about how to use SONAMEs in C/C++ libraries,
resulting in more usable libraries.
--
Hubert Chathi <uho...@debian.org> -- https://www.uhoreg.ca/
Jabber: hub...@uhoreg.ca -- Matrix: @uhoreg:matrix.org
PGP/GnuPG key: 4096R/F24C F749 6C73 DDB8 DCB8
ires foo. I think the second option is the best,
especially since Node upstream seems to prefer searching for things in
node_modules rather than in /usr/lib/nodejs. And again, we may want to
create a transitional package node-foo that symlinks /usr/lib/nodejs/foo
to /usr/lib/nodejs/fooVER.
