Quoting Pirate Praveen (2021-01-08 12:16:20) > > > On Fri, Jan 8, 2021 at 12:06 pm, Jonas Smedegaard <jo...@jones.dk> > wrote: > > Quoting Pirate Praveen (2021-01-08 11:55:14) > >> > >> > >> On 2021, ജനുവരി 8 1:16:36 PM IST, Paolo Greppi > >> <paolo.gre...@libpf.com> wrote: > >> >BTW, why is node-babel7 a run-time dependency of yarnpkg ? > >> >Should it not just be a build-dep ? > >> > > >> > >> It needs @babel/runtime which is currently part of node-babel7. I > >> think yadd already uploaded a version of node-babel7 with separate > >> node-babel7-runtime binary package. But it has not cleared NEW yet. > > > > You need not wait for NEW clearance to depend explicitly on required > > packages - you need only have the required packages available as > > virtual packages. > > > > Yes, but changing dependency alone will not solve this issue. When it > clears NEW and dependency is updated, this bug will be fixed for > yarnpkg, but node-babel7 will still be affected.
I don't understand - how is node-babel7 affected by how yarnpkg declares (build-)dependencies against it? What I suggest is to improve the package yarnpkg to replace any runtime and build-time package relations on node-babel7 to instead be on each actually needed node-$module package, virtual or not. (and yes, it should work fine for autopkgtest as well - a previous failure I caused was due to lack of appending (>= 7) for a virtual package also provided by older babel6 package). - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: signature
-- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel