Package Details: svgo 2.3.0-1

Git Clone URL: https://aur.archlinux.org/svgo.git (read-only, click to copy)
Package Base: svgo
Description: Tool for optimizing SVG files
Upstream URL: https://github.com/svg/svgo
Licenses: MIT
Conflicts: nodejs-svgo
Provides: nodejs-svgo
Replaces: nodejs-svgo
Submitter: flacks
Maintainer: simon04
Last Packager: simon04
Votes: 23
Popularity: 0.160687
First Submitted: 2018-07-24 18:35
Last Updated: 2021-04-03 21:49

Required by (4)

Sources (1)

Latest Comments

1 2 Next › Last »

simon04 commented on 2021-03-27 09:36

Thanks, fixed in 2.2.2-2 (what a lucky number) – https://aur.archlinux.org/cgit/aur.git/commit/?h=svgo&id=5c5bc629b2cd8662125731d1e1840c3008387431

eugene commented on 2021-03-23 16:16

npm install line should not have --user root as new guidelines suggest

flipflop97 commented on 2021-03-23 14:42

@1ace

Same issue with package semver

1ace commented on 2021-03-20 11:18

This package installs a bunch of files in /usr/lib/node_modules/root/ (as well as the normal /usr/lib/node_modules/svgo/), which conflicts with vscode-html-languageserver for instance as that package tries to do the same; I'm not sure if this "root" module is really a thing that should be installed ("root" may very well be a placeholder name), but I'm guessing neither packages should be doing this :)

PanisSupraOmnia commented on 2019-04-25 20:36

Correct me if I'm wrong, but shouldn't the npm install line have --user root passed to it, per the Arch wiki? The current PKGBUILD causes the files to be owned by the installing user.

Edit: Also, you specify that the license is MIT; however, Arch takes MIT as a special case of a custom license, in that you need to install the license in the PKGBUILD because it has a copyright line. See the Arch wiki for details. I happened to notice these issues because I ran namcap on the package.

tensor5 commented on 2018-02-09 17:05

I've seen this issue in other npm packages, it didn't show up in my build though.

Calimero commented on 2018-02-09 14:35

I wanted to ask for a fix of the permission issues: there are lots of files and directories with mode 777. But installing a second time fixes that, I'm not sure what's happening.

tensor5 commented on 2017-11-17 10:51

@Enverex, do you have that permission mismatch only on /usr/bin?

Enverex commented on 2017-11-16 15:40

Also worth fixing this...

warning: directory permissions differ on /usr/bin/
filesystem: 755 package: 777

JP-Ellis commented on 2017-05-30 01:20

@tensor5, could you either update the PKGBUILD or disown it? It's been flagged out-of-date since October last year :/