[Pkg-javascript-devel] Comments regarding acorn_6.1.1+ds+~0.3.1+~4.0.0+~1.0.0+~5.0.1+ds+~1.6.2+ds-1_amd64.changes

[Xavier]

Le 05/08/2019 à 14:20, Pirate Praveen a écrit :
> 
> 
> On 2019, ഓഗസ്റ്റ് 5 5:42:17 PM IST, roucaries bastien <roucaries.bastien+debian at gmail.com> wrote:
>> In
>> On Mon, Jul 8, 2019 at 2:26 PM Chris Lamb <lamby at debian.org> wrote:
>>>
>>> Dear Jonas et al.,
>>>
>>>> What would you suggest/expect as more useful alternative - given
>> the
>>>> constraint set by ftpmasters?
>>>
>>> If I may be so bold: this seems to be a hot button topic for you or I
>>> am somehow entirely incorrectly reading adverserial animosity in the
>>> tone of both your messages. This would, if only practically speaking,
>>> not feel like a terribly productive mode of discussion so I do hope
>>> you that in the event you felt you needed to comment any further you
>>> would be able to ally and assuage me on this angle.
>>>
>>> To be clear, I don't have any suggestions (do note I was quite-
>>> literally "musing out loud"), I was merely explicitly noting a slight
>>> wart in the current state of affairs that might be taken into account
>>> if, completely and entirely hypothethically, any of this revisied or
>>> reviewed more generally. I trust this clarifies my position. :)
>>
>> Going back to debian after a short hiatus (we are expected our 3d
>> child in four year in october), I do not see anything offensing in
>> your tone.
>>
>> The next version of acorn will be worst from this point of view:
>> 6.2.1+ds+~0.4.0+~4.0.0+really4.0.0+~1.0.0+~5.0.1+ds+~1.7.0+ds+~0.1.1+~0.3.1+~0.2.0+~0.1.0+~0.3.0+~0.3.0
>>
>> upstream split small package in smaller package, so we try to do our
>> best.
>>
>> I was thinking first to using a sequence number but we lost the uscan
>> automatic up to date download.
>>
>> In fact we exchanged small insane package we insane metadata, against
>> a crazy version string, I believe it is a fair engineering decision.
>> We push the whole crap only to one place a version string.
>>
>> Bastien
> 
> I think this is over engineering. We can just embed smaller modules multiple times instead. If something is not small enough to embed, I think it is worth tracking it as a separate package.

Hi, +1

using pkg-js-tools auto_installer, components will be installed
automatically in usr/share/acorn/node_modules/ unless specified in
debian/nodejs/<component>/install.

Also if upstream provides a package-lock (or yarn.lock), you can safely
use "ignore" in debian/watch for components installed in
usr/share/acorn/node_modules/

Cheers,
Xavier