[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#961337: Bug#986737: RFS: deno/1.8.3-1 [ITP] -- A secure JavaScript and TypeScript runtime



(please don't top-post)
(cc-ing to relevant bugs and teams)


Le sam. 10 avr. 2021 à 22:26, Sergey Abroskin <merdedok@gmail.com> a écrit :
On Sat, Apr 10, 2021, 23:18 Jérémy Lal <kapouer@melix.org> wrote:


Le sam. 10 avr. 2021 à 21:42, Geert Stappers <stappers@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.
> Deno has ~400 dependencies. What should I do?

For all that concerns building:
https://wiki.debian.org/Teams/RustPackaging

For all that concerns userland:
https://wiki.debian.org/_javascript_
In particular this is very interesting to read (because it explains what could be bundled or not):
https://wiki.debian.org/_javascript_/GroupSourcesTutorial

Debian toolchains have been upgraded (mainly by DD yadd) to cope with bundled dependencies,
A.K.A. components. Uscan now supports this.

In my experience a huge project like Deno is going to drag sub-projects, make them live,
and also make mistakes and depend on abandonware.
This isn't going to be a piece of cake. The more Deno and its deps are stable, the more it's going to be easy to package.

Jérémy

Reply to: