Le sam. 10 avr. 2021 à 21:42, Geert Stappers <stapp...@debian.org> a écrit :
> On Sat, Apr 10, 2021 at 09:17:12PM +0300, Sergey Abroskin wrote: > > Dear mentors, > > > > I am looking for a sponsor for my package "deno": > > > > * Package name : deno > > Version : 1.8.3-1 > > Upstream Author : The Deno Authors > > * URL : https://deno.land > > > > > > https://mentors.debian.net/package/deno/ > > > > dget -x > https://mentors.debian.net/debian/pool/main/d/deno/deno_1.8.3-1.dsc > > > > * Initial release (Closes: 961337) > > > > <screenshot> > stappers@paddy:/usr/src/debian/deno > $ grep ^name Cargo.lock | head > name = "Inflector" > name = "adler" > name = "ahash" > name = "ahash" > name = "aho-corasick" > name = "alloc-no-stdlib" > name = "alloc-stdlib" > name = "ansi_term" > name = "anyhow" > name = "anymap" > stappers@paddy:/usr/src/debian/deno > $ grep --after=1 ^Build-Depends debian/control > Build-Depends: debhelper (>= 11), rustc, cargo > Standards-Version: 4.1.3 > stappers@paddy:/usr/src/debian/deno > $ > </screenshot> > > What cargo needs doesn't match the Build-Depends. > If uploaded, it would fail to build due missing build dependencies. > > > Yes, consider packaging deno for Debian (and it's derivatives) > a very interresting challenge. > Hi ! Deno is Javascript/Typescript ! Please cc and involve pkg-javascript team. Issues are 3-fold: - packaging cargo (rust's package manager) dependencies - how Deno userland modules (written in typescript/javascript) are going to be distributed (probably in a way comparable to how node or javascript modules are distributed) - https://github.com/denoland/rusty_v8 how to make Node and Deno share the same v8. (This is where i might be able to help). Jérémy
