On 2/20/25 11:56, Khalid Masum wrote:
Hi Jérémy,
On Wed, Feb 19, 2025 at 4:02 PM Jérémy Lal <kapo...@melix.org> wrote:
Hi,
Le mer. 19 févr. 2025 à 05:06, Khalid Masum <khalid.masum...@gmail.com> a écrit
:
Hello,
I would like to collaborate with the emscripten package and in the bug tracker
Jeremy asked me to contact here.
I was able to pull the latest version and build it (Thanks for fixing the
3.1.66 bugs!). What should be my next step?
If you didn't build it using sbuild, please start by doing that.
https://wiki.debian.org/sbuild
I suggest the unshare backend.
for emscripten:
- address lintian warnings (https://tracker.debian.org/pkg/emscripten)
- address lintian informations (lintian -I after a build)
- bug triage
https://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no&src=emscripten
Ask me about how to close a bug or mark it as fixed in version x.
for binaryen:
- third_party directory has sources that are available in other debian packages,
binaryen should use them, also make sure you understand Built-Using field of
debian/control,
and the difference with Static-Built-Using (I don't).
- fix lintian, reproducibility, build logs checks...
https://tracker.debian.org/pkg/binaryen
Jérémy
Thank you! I have built the package with sbuild successfully. However
I have a question
regarding this.
I followed these steps:
- I cloned the git repository from salsa:
https://salsa.debian.org/debian/emscripten
- cd emscripten
- git archive --format=tar.gz
--output=../emscripten_3.1.69+dfsg.orig.tar.gz HEAD
- sbuild
My question is, is everything alright with this workflow?
Hi,
no it is not: orig.tar.gz file is the unmodified source (except dfsg).
See https://wiki.debian.org/Javascript/Tutorial
Best regards,
Xavier
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
