On March 12, 2018 3:34:26 AM GMT+05:30, Bastien ROUCARIES
wrote:
>Done for node-has using node-function-bind but it break uscan for
>node-has
>
>Bill could you get a glimpse, I will like to create something more
>robust
I think it is better to create a native Debian package (so no need for usc
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 വെള്ളി 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 വെള്ളി 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
On ചൊവ്വ 06 മാർച്ച് 2018 07:57 വൈകു, Ian Jackson wrote:
> Simon is asking the same questions as I was earlier. Sorry for
> posting before reading the whole thread.
>
> Is this going to be common ? The Javascript ecosystem has large
> numbers of small packages - but do they mostly contain just JS
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 t
On വെള്ളി 02 മാർച്ച് 2018 09:57 വൈകു, Jonas Smedegaard wrote:
> I generally read team policies with an implicit "...as long as it
> doesn't conflict with the general Debian Policy".
>
> Specifically, I read the "should" in above quote as "in most cases, but
> not a "must".
>
> We have in the Ja
On March 4, 2018 3:15:24 AM GMT+05:30, Simon McVittie wrote:
>Am I right in saying that nodejs-handlebars (or libjs-handlebars or
>some
>such) contains both a command-line tool, handlebars(1) (or similar),
>and
>a library named handlebars for node.js?
Yes. handlebars binary package includes /us
On വെള്ളി 02 മാർച്ച് 2018 09:57 വൈകു, Jonas Smedegaard wrote:
> I generally read team policies with an implicit "...as long as it
> doesn't conflict with the general Debian Policy".
>
> Specifically, I read the "should" in above quote as "in most cases, but
> not a "must".
>
> We have in the Ja
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-poli
[As suggested by Ian Jackson on -devel] [0]
Hi,
Javascript maintainers team have evolved a policy for javascript
packages and it is available at https://wiki.debian.org/Javascript/Policy
Its last point says,
5. should generate a node-foo binary package if the script is usable
also for Nodejs
Bu
12 matches
Mail list logo
