On Sun, Mar 11, 2018 at 02:48:40PM +0530, Pirate Praveen wrote:
> > * Some Javascript modules are very small, resulting in lots of small
> > packages
>
> I think we need to balance the small packages concern with number of
> times such small packages are used.
>
> node-has was rejected recently
On ഞായര് 11 മാർച്ച് 2018 04:59 വൈകു, Simon McVittie wrote:
> The reason I suggested that restriction was to avoid having contradictory
> requirements: if node-foo is the naming convention for the module
> that lets nodejs users require('foo'), and node-foo is also the naming
> convention for a nod
On Sun, 11 Mar 2018 at 14:48:40 +0530, Pirate Praveen wrote:
> On വെള്ളി 09 മാർച്ച് 2018 08:39 വൈകു, Simon McVittie wrote:
> > And for executables, perhaps something like this:
...
> > * should not be named node-* without a suffix like -bin or -tools (?)
>
> I don't think there is any particular b
On വെള്ളി 09 മാർച്ച് 2018 08:39 വൈകു, Simon McVittie wrote:
> I think saying "script" is perhaps unhelpful here, because outside
> Javascript, that usually refers to something executable with #! at the
> beginning.
>
> It might be clearer to think about this in terms of libraries and
> executables
On Tue, Mar 06, 2018 at 02:12:52PM +, Ian Jackson wrote:
> Pirate Praveen writes ("Javascript team policy and rejection of node-three
> binary package"):
> > 1. Node.js has standard locations for discovering installed packages
> > which is different from browser targeted javascript libraries.
Pirate Praveen writes ("Re: Javascript team policy and rejection of node-three
binary package [and 1 more messages]"):
> On വെള്ളി 09 മാർച്ച് 2018 04:48 വൈകു, Ian Jackson wrote:
> > [Pirate:]
> >> I think the following change to point 5 of javascript polic
On Fri, 09 Mar 2018 at 17:50:30 +0530, Pirate Praveen wrote:
> How about the change given below? (is the intent clear at least even if
> disagreement on content remains)
>
> 5. should add 'Provides: node-foo' in debian/control and install
> package.json in /usr/lib/nodejs/foo, if the script is usa
On വെള്ളി 09 മാർച്ച് 2018 04:48 വൈകു, Ian Jackson wrote:
> But:
>
>> 2. We won't be able to specify a minimum version of nodejs for these
>> modules. For example, node-regexpu-core required nodejs >= 6 and
>> this prevented its testing migration for a long time because testing
>> only had nodejs
Pirate Praveen writes ("Re: Javascript team policy and rejection of node-three
binary package"):
> On ചൊവ്വ 06 മാർച്ച് 2018 07:42 വൈകു, Ian Jackson wrote:
> > This could be solved by dropping the nodejs dependency from all the
> > nodejs module packages and requiring
On ചൊവ്വ 06 മാർച്ച് 2018 07:52 വൈകു, Ian Jackson wrote:
> I do think that the Javascript policy has to be not in a wiki page.
> We can't have normative references from debian-policy to wiki pages.
>
> Pirate, is there some Debian-specific Javascript dev infrastructure
> package that could host thi
On ചൊവ്വ 06 മാർച്ച് 2018 07:42 വൈകു, Ian Jackson wrote:
> Pirate Praveen writes ("Javascript team policy and rejection of node-three
> binary package"):
>> 1. Node.js has standard locations for discovering installed packages
>> which is different from browser targeted javascript libraries.
>>
>> N
Hello Ian,
On Tue, Mar 06 2018, Ian Jackson wrote:
> Thanks for bringing this up, here. FAOD, my primary intent in
> suggesting you do so was to get technicaly input from the denizens of
> d-policy, who have a lot of useful expertise.
Okay. It's fine to use this list for that, of course.
I ha
Sean Whitton writes ("Re: Javascript team policy and rejection of node-three
binary package"):
> On Fri, Mar 02 2018, Pirate Praveen wrote:
> > I think the policy is good and request debian policy team to endorse
> > it.
Thanks for bringing this up, here. FAOD, my pri
Pirate Praveen writes ("Javascript team policy and rejection of node-three
binary package"):
> 1. Node.js has standard locations for discovering installed packages
> which is different from browser targeted javascript libraries.
>
> Node.js expects pure js modules to be installed at /usr/lib/node
Pirate Praveen wrote:
> md5sum /usr/share/javascript/backbone/backbone.js
> /usr/lib/nodejs/backbone/index.js
> 8a8d829617513f36185a0ab055d088ec
> /usr/share/javascript/backbone/backbone.js
> 8a8d829617513f36185a0ab055d088ec /usr/lib/nodejs/backbone/index.js
except
lrwxrwxrwx … /usr/lib/nodejs
On വെള്ളി 02 മാർച്ച് 2018 09:25 വൈകു, Sean Whitton wrote:
> Hello,
>
> On Fri, Mar 02 2018, Pirate Praveen wrote:
>
>> I think the policy is good and request debian policy team to endorse
>> it.
>
> The way forward is to add the JavaScript policy to the debian-policy
> package. It would not be
Hello,
On Fri, Mar 02 2018, Pirate Praveen wrote:
> I think the policy is good and request debian policy team to endorse
> it.
The way forward is to add the JavaScript policy to the debian-policy
package. It would not be wise to add a single requirement to our
document, with the rest of the Jav
On Fri, Mar 02, 2018 at 07:56:40PM +0530, Pirate Praveen wrote:
> Node.js expects pure js modules to be installed at /usr/lib/nodejs but
> javascript libraries are installed at /usr/share/javascript
Why should pure js module be in /usr/lib instead of /usr/share ?
Cheers,
--
Bill.
Imagine a lar
18 matches
Mail list logo
