[Pkg-javascript-devel] Bug#962039: Bug#962037: Bug#962037: Plan B for not being able to replicate upstream exports exactly

[Pirate Praveen]

On Mon, Jun 15, 2020 at 4:07 pm, Pirate Praveen 
<praveen at onenetbeyond.org> wrote:
> Please don't invent your own methods and follow the standards used by 
> the rest of the team. If everyone invents their own methods to embed, 
> that makes it unnecessarily hard to collaborate as a team. I don't 
> think the rest of the js team agrees with your judgement here. This 
> method makes is harder to update embedded dependencies and it 
> essentially become a fork. You can use the normal patching workflow 
> with quilt for modules embedded via pkg-js-tools (it is not even 
> specific to pkg-js-tools, it is supported by dpkg and used across the 
> archive).
> 
> Js Team,
> 
> Please comment your opinion here as we have a difference in embed 
> strategy here.

Just a clarification, there are two ways of embedding modules, 1, using 
debian/watch component with debian/gbp.conf and 2, adding to 
debian/build_modules or debian/test_modules

Only method 1 allows using quilt patching. I assume he was referring to 
method 2. I was referring to method 1.