On Sat, 2021-09-04 at 17:08 +0200, Axel Beckert wrote: > Also it is unclear to me why the source is the Mozilla XPI while the > package works with both and upstream offers different download files > for Firefox and for Chromium/Chrome. (Then again, I haven't worked on > browser extensions since Mozilla ditched XUL…)
I tried updating webext-umatrix to the latest release and immediately encountered this issue too as the build fails with the upstream source instead of the upstream prebuilt XPI file. I think that using prebuilt XPI files when the upstream project has a git repository has a risk of DFSG item 2 violations. Debian using XPI files is one of the reasons I started this discussion about not using upstream packaging ecosystems: Debian choice of upstream tarballs for packaging https://lists.debian.org/msgid-search/937697e40caf519e18119635db07d7b74b37b980.ca...@debian.org That said, I expect building WebExtensions from source properly is going to be a large undertaking that will require lots of node-* packages and other dependencies to be added to Debian. So a reasonable way to start is probably to update to the latest XPI and then start working on the dependencies etc. -- bye, pabs https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
