Il 13/04/2018 10:29, Pirate Praveen ha scritto: > Hi, > > I was hoping to be able to package all node dependencies of gitlab in main, > though the sheer number of them made ftp masters to ignore them. I understand > that kind of numbers are quite intimidating to deal with, so I have already > moved gitlab to contrib and install these node modules directly from npm > registry. > > But even that cannot move to buster because npm is not yet in buster, which > is also stuck in NEW. So I'm thinking of adding yarn also to contrib, > bundling all dependencies. If the node modules in NEW starts moving, > hopefully when next batch of ftp assistants are on boarded, we can get it to > main. > > This will also help me in backporting gitlab 10 to stretch as backporting > security fixes to 8.13 is pretty challenging. > --
Why not ? We can pursue yarn packaging to contrib in parallel with the mid-term task of bringing it back to main. This is best handled with a separate git branch (master-contrib ?) I am ready to give it a try. The missing dependencies can be individually npm install-ed. Two options I can think of: - providing the resulting node_modules directory as a huge patch - running npm install xxx ... in debian/rules which is best ? Paolo P.S. yarn 1.6.0 is out, I am updating the repo just now
