Package Details: inkscape-git 5:1.3.alpha.r987.g07fdc5641e-1

Git Clone URL: https://aur.archlinux.org/inkscape-git.git (read-only, click to copy)
Package Base: inkscape-git
Description: An Open Source vector graphics editor, using SVG file format, from git master
Upstream URL: https://gitlab.com/inkscape
Licenses: GPL, LGPL
Conflicts: inkscape
Provides: inkscape
Submitter: haawda
Maintainer: bartus
Last Packager: bartus
Votes: 7
Popularity: 0.180862
First Submitted: 2017-06-10 19:46 (UTC)
Last Updated: 2024-03-13 13:21 (UTC)

Required by (165)

Sources (9)

Pinned Comments

bartus commented on 2023-11-11 20:47 (UTC) (edited on 2023-11-11 20:51 (UTC) by bartus)

This package is also hosted on GitHub.
Use env vars to control build process:
  • BITMAP_BACKEND={imagemagick,graphicsmagick} change bitmap filter backend (default imagemagick(libmagick6))
  • MAKEFLAGS="xxx" to override default make flags.
Usage cases:
  • makepkg BITMAP_BACKEND=graphicsmagick MAKEFLAGS=-j1
  • yay -S gimp-git --mflags "BITMAP_BACKEND=graphicsmagick;MAKEFLAGS=-j1"

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »

bartus commented on 2019-08-01 16:55 (UTC) (edited on 2019-08-01 16:57 (UTC) by bartus)

Yep, you will need to add -D default_library=both to arch-meson and options=(staticlibs) to pango PKGBUILD for this. Than move pango form deps to makedeps and force static linking to prevent conflict with system wide pango=144 ...

I've tried this, but thought quick patch would be simpler for common user to handle

haawda commented on 2019-08-01 15:38 (UTC)

Thanks, I was not even aware of the problem. And well, lilypond suffers of the same.

If upstream has no quick fix, someone should consider to provide a package pango143, which should be installable alongside pango.

bartus commented on 2019-08-01 12:36 (UTC) (edited on 2019-08-01 14:45 (UTC) by bartus)

@haawada: I've noticed, inkscape won't build against pango=1.44. I've made a hacky patch to resolve the issue...

bradst commented on 2019-06-01 11:47 (UTC)

Per http://wiki.inkscape.org/wiki/index.php/Release_notes/1.0:

"Inkscape now uses a git submodule for the extensions directory. If you have cloned the repository and are not building from the release source code tarball, please note the updated build instructions"

Currently the submodule is uninitialized. Adding this line to prepare() should fix it:

git submodule update --init --recursive

haawda commented on 2019-04-28 15:43 (UTC)

Applied, thanks.

lonaowna commented on 2019-04-28 14:22 (UTC) (edited on 2019-04-28 14:23 (UTC) by lonaowna)

Hi, can you please make these changes?

Update the url field (Launchpad is no longer used):

url="https://gitlab.com/inkscape/inkscape"

Change the python2 dependencies to python, since "Inkscape's stock extensions have been moved to their own repository and were updated for compatibility with Python 3".

depau commented on 2019-04-19 23:38 (UTC)

@lugao feel free to add it to the AUR anyway

haawda commented on 2019-04-19 15:26 (UTC)

I do not think that shallow clones are a good idea at all. I will not incorporate your change. Feel free to keep your package in AUR.

lugao commented on 2019-04-19 12:30 (UTC) (edited on 2019-04-19 12:31 (UTC) by lugao)

I created a derived package called inkscape-shallow-git to only shallow clone the inkscape repository. The full clone downloads about 1.6 GiB and the shallow clone about 27.72 MiB.

@haawad: Do you think you could integrate it into your package? Thanks!

friday13 commented on 2019-02-13 09:09 (UTC)

(inkscape:1259): Gtk-WARNING **: 12:09:23.554: Unable to locate theme engine in module_path: "adwaita",

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »