Project

General

Profile

Freedom issue #2527

[asar]: depends on electron

bill-auger - about 1 year ago - . Updated about 1 year ago.

Status:
fixed
Priority:
freedom issue
Assignee:
% Done:

0%


Description

'asar' is just a re-packaging of the node package via `npm install --global` in the package() function - that pulls in electron fro the webby-web-web; so that electron does not appear in the depends() array - sneaky, huh

https://github.com/electron/asar/blob/v2.0.1/package.json#L42


Related issues

Related to Packages - Freedom issue #1167: [chromium][qt5-webengine][electron] QTWebgine/Electron embeds "entire Chromium platform"confirmed

Actions

History

#1

Updated by bill-auger about 1 year ago

  • Related to Freedom issue #1167: [chromium][qt5-webengine][electron] QTWebgine/Electron embeds "entire Chromium platform" added
#2

Updated by bill-auger about 1 year ago

  • Status changed from in progress to fixed
#3

Updated by eschwartz about 1 year ago

That is a devDependency, it is not used in the PKGBUILD -- did you even check this?

Report a bug to archlinux for downloading the source code in package, fine. Blacklist the entire nodejs ecosystem because literally not one package ever builds without downloading at least something from the internet -- okay, I'm agreeable to that.

But don't say asar depends on electron unless it actually does.

I ASSURE you, there is no way ever under any circumstances ever, that a package with arch=('any') is downloading and installing some ELF binaries from the "webby-web-web". Or even packaging them at all.

#4

Updated by bill-auger about 1 year ago

i didnt mean for that to be so pedantic - im not sure if the
node package includes any binaries - i would have looked deeper
if i thought this was something that we could keep

the main thing is that this program appears to useful only for
the purpose of creating electron apps - even if electron is not
part of the packaged program itself and even if the PKGBUILD did
not download it, that would still be "suggesting" to use
electron by the FSDG guidelines, if the program has no other
use-case

if the program does have a valid use-case that does not
necessarily suggest electron then theres probably no problem
with bringing it back

Also available in: Atom PDF