On Fri, Feb 18, 2022 at 3:21 PM Fabio Valentini decathorpe@gmail.com wrote:
On Fri, Feb 18, 2022 at 3:14 PM IƱaki Ucar iucar@fedoraproject.org wrote:
What kind of issues? Aren't they MIT licensed?
Some of them are MIT licensed, some are not, but many do not correctly contain license files. I tried listing all the ones that don't in the TODO section on the GitHub repo I linked above.
And when you talk about "packages" in this context, what does it mean? Are they parts of the main repo? Or third-party modules? I assume it's not what they call the "standard library", because that's JavaScript and TypeScript.
I mean the packages for invidivual Rust dependencies. Some of them are part of the deno project (backend libraries for the "deno" runtime binary, which provide networking, crypto, filesystem access, etc. functionality for the runtime). But those also depend on a a lot of other Rust libraries, among them the dozens of crates that make up SWC (the typescript compiler they use), which is a separate project entirely The problems I see is that some crates do not publish sources with licenses files as they should, and one of the deno projects (rusty_v8) bundles sources for the V8 runtime from chromium, but doesn't include license files for all bundled components.
Sorry, hit send too soon.
Basically, maintaining a "properly done" package of deno for Fedora would be a full-time job, because of the sheer number of individual components, which also mostly need to be updated in a coordinated fashion. Which is why I only had time to do the initial packaging for COPR, and one big batch of updates, but then fell behind upstream releases, just because it's just so time-consuming.
Fabio