Bug#991761: rust-swc-core: ecma crates ready to enable (ITP #991761)
Juan M. Méndez Rey <[email protected]> Tue, 21 Jul 2026 09:50:21 +0000
| Newsgroups | gmane.linux.debian.devel.wnpp |
|---|---|
| Message-ID | <eyEPovUFJISyl9MK83xkWkea7sgSdAnJ7O5WfQYCDjGYiUj5PowiNp1WVGIpWwobv4ZnkaEfWsHEencWn39yjiWTFjb1PPVX2BN9HjvQHzw=__6521.34304852865$1784627609$gmane$org@proton.me> |
Hi Jonas, Answering below > Oh - sorry, but I have in the meantime updated the pacakage, so your > patch no longer applies. Also, it turns out that swc_ecma_preset_env > needs precomputed-map which needs packaging. Can you do that? > > What I would prefer is that instead of a single giant git commit with > all changes that you instead could prepare a set of git commits with > more narrow, "atomic" commits. It is fine that you share in your > private branch as you have done above, then I can cherry-pick from > there. Regarding precomputed-map. MR ready for debcargo-conf: https://salsa.debian.org/rust-team/debcargo-conf/-/merge_requests/1283 (ITP #1142523) Now: ecma crates. Changed now to 3 atomic commits (as requested) on debian/enable-ecma-crates-v2 in my fork: https://salsa.debian.org/mendezr/rust-swc-core/-/commits/debian/enable-ecma-crates-v2 I took a look to the the icu_properties exclusion (to enable ecma_minifier/transforms) but it is a different matter in scope, so I think it is better to work on that on a different batch of work. The dev-dep chain cascades and rollup doesn't need those, my main objective to unblock rollup-v4 Please, have a look, Juan