rsvg2 3.2.3-x64-mingw32 → 3.2.4-x64-mingw32

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 882875b9fde7facfba165bb1ba208f2123fab8e3245f9801013e032115cc16b5
-  data.tar.gz: 3965924033a501ae748c638f3b0c1681d1241aaae4819c74e084f3ffbf30176c
+  metadata.gz: f016f543eee7d7a0c2257e48f9261d011b3f6cfafcdbe6deac4c1bee37660756
+  data.tar.gz: 59c29cca1983c05e17a7d888e85d9608b78d48009ada7ef79ab1653d5a78c9ee
 SHA512:
-  metadata.gz: 4a80d3379b70914301ad4dbbceae87b46d2b612f33a6a2eda720a976bdc887c2a5acabfc52a1ff2ff0047375faade242383af3cc017513285dd0baa372c16dc8
-  data.tar.gz: 8577c6abd9673b467b9da6da6e0a749164b0bd62c7e36e37a955d88620cb5bce1acfd4013636f42f17029b930e32223d2a7bcf6b07db8b8e29dbeb18f7ee079a
+  metadata.gz: 80e8f5c43f6845a33cd45bf06badb4f9afe6183f9973b5ddff52952b2aac53189315a9d1bd6bebf538ae80590c743cab2837e0097b029c6c3707ff543326618a
+  data.tar.gz: ed575f7a3003e8e531420189b79f95224c485e4b364e53c39eff4c4c108b0bee473ad1ca53ef6e652789ed326c4ec0fab256d65eee38e839e0cfb9331496c8ab

data/Rakefile

@@ -1,6 +1,6 @@
 # -*- ruby -*-
 #
-# Copyright (C) 2010-2017  Ruby-GNOME2 Project Team
+# Copyright (C) 2010-2018  Ruby-GNOME2 Project Team
 #
 # This library is free software; you can redistribute it and/or
 # modify it under the terms of the GNU Lesser General Public
@@ -64,14 +64,17 @@ package_task = GNOME2::Rake::PackageTask.new do |package|
       :name => "librsvg",
       :download_site => :gnome,
       :label => "librsvg",
-      :version => "2.40.20",
+      :version => "2.42.3",
       :compression_method => "xz",
       :windows => {
         :configure_args => [
           "--enable-introspection",
         ],
         :patches => [
+          "librsvg-2.42-cross-compile.diff"
         ],
+        :need_autoreconf => true,
+        :force_to_disable_deplibs_check => true,
         :built_file => "bin/librsvg-2-2.dll",
       },
     },

data/vendor/local/include/librsvg-2.0/librsvg/librsvg-enum-types.h

@@ -11,7 +11,7 @@
 #include <glib-object.h>
 
 G_BEGIN_DECLS
-/* enumerations from "rsvg.h" */
+/* enumerations from "librsvg/rsvg.h" */
 GType rsvg_error_get_type (void);
 #define RSVG_TYPE_ERROR (rsvg_error_get_type())
 GType rsvg_handle_flags_get_type (void);

data/vendor/local/include/librsvg-2.0/librsvg/librsvg-features.h

@@ -6,9 +6,9 @@
 #define LIBRSVG_FEATURES_H
 
 #define LIBRSVG_MAJOR_VERSION (2)
-#define LIBRSVG_MINOR_VERSION (40)
-#define LIBRSVG_MICRO_VERSION (20)
-#define LIBRSVG_VERSION "2.40.20"
+#define LIBRSVG_MINOR_VERSION (42)
+#define LIBRSVG_MICRO_VERSION (3)
+#define LIBRSVG_VERSION "2.42.3"
 
 #define LIBRSVG_CHECK_VERSION(major,minor,micro) \
   (LIBRSVG_MAJOR_VERSION > (major) || \

data/vendor/local/include/librsvg-2.0/librsvg/rsvg-cairo.h

@@ -1,5 +1,5 @@
-/* -*- Mode: C; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4 -*- */
-/* vim: set sw=4 sts=4 ts=4 expandtab: */
+/* -*- Mode: C; indent-tabs-mode: nil; c-basic-offset: 4 -*- */
+/* vim: set sw=4 sts=4 expandtab: */
 /* 
    rsvg-cairo.h: SAX-based renderer for SVG files using cairo
  

data/vendor/local/include/librsvg-2.0/librsvg/rsvg.h

@@ -1,5 +1,5 @@
-/* -*- Mode: C; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 4 -*- */
-/* vim: set sw=4 sts=4 ts=4 expandtab: */
+/* -*- Mode: C; indent-tabs-mode: nil; c-basic-offset: 4 -*- */
+/* vim: set sw=4 sts=4 expandtab: */
 /* 
    rsvg.h: SAX-based renderer for SVG files into a GdkPixbuf.
  
@@ -65,11 +65,6 @@ typedef enum {
 #define RSVG_ERROR (rsvg_error_quark ())
 GQuark rsvg_error_quark (void) G_GNUC_CONST;
 
-/**
- * RsvgHandle:
- *
- * The #RsvgHandle is an object representing the parsed form of a SVG
- */
 typedef struct _RsvgHandle RsvgHandle;
 typedef struct RsvgHandlePrivate RsvgHandlePrivate;
 typedef struct _RsvgHandleClass RsvgHandleClass;
@@ -80,7 +75,7 @@ typedef struct _RsvgPositionData RsvgPositionData;
  * RsvgHandleClass:
  * @parent: parent class
  *
- * Class structure for #RsvgHandle
+ * Class structure for #RsvgHandle.
  */
 struct _RsvgHandleClass {
     GObjectClass parent;
@@ -89,6 +84,12 @@ struct _RsvgHandleClass {
     gpointer _abi_padding[15];
 };
 
+/**
+ * RsvgHandle:
+ * @parent: parent instance
+ *
+ * Lets you load SVG data and render it.
+ */
 struct _RsvgHandle {
     GObject parent;
 
@@ -127,7 +128,10 @@ struct _RsvgPositionData {
 
 void rsvg_cleanup (void);
 
+RSVG_DEPRECATED
 void rsvg_set_default_dpi	(double dpi);
+
+RSVG_DEPRECATED
 void rsvg_set_default_dpi_x_y	(double dpi_x, double dpi_y);
 
 void rsvg_handle_set_dpi	(RsvgHandle * handle, double dpi);
@@ -219,7 +223,7 @@ void rsvg_handle_free (RsvgHandle * handle);
  * Deprecated: Set up a cairo matrix and use rsvg_handle_render_cairo() instead.
  * See the documentation for rsvg_handle_set_size_callback() for an example.
  */
-typedef /* RSVG_DEPRECATED */ void (*RsvgSizeFunc) (gint * width, gint * height, gpointer user_data);
+/* RSVG_DEPRECATED */ typedef void (*RsvgSizeFunc) (gint * width, gint * height, gpointer user_data);
 
 RSVG_DEPRECATED
 void rsvg_handle_set_size_callback (RsvgHandle * handle,

data/vendor/local/lib/librsvg-2.la

@@ -1,5 +1,5 @@
 # librsvg-2.la - a libtool library file
-# Generated by libtool (GNU libtool) 2.4.6
+# Generated by libtool (GNU libtool) 2.4.6 Debian-2.4.6-2
 #
 # Please DO NOT delete this file!
 # It is necessary for linking the library.
@@ -17,15 +17,15 @@ old_library='librsvg-2.a'
 inherited_linker_flags=' -pthread'
 
 # Libraries that this one depends upon.
-dependency_libs=' -R/home/vagrant/ruby-gnome2/glib2/vendor/local/lib -L/home/vagrant/ruby-gnome2/glib2/vendor/local/lib -L/home/vagrant/rcairo/vendor/local/lib -L/home/vagrant/ruby-gnome2/rsvg2/vendor/local/lib -L/home/vagrant/ruby-gnome2/pango/vendor/local/lib -L/home/vagrant/ruby-gnome2/gdk_pixbuf2/vendor/local/lib /home/vagrant/ruby-gnome2/gdk_pixbuf2/vendor/local/lib/libgdk_pixbuf-2.0.la /home/vagrant/ruby-gnome2/glib2/vendor/local/lib/libgio-2.0.la /home/vagrant/ruby-gnome2/glib2/vendor/local/lib/libgmodule-2.0.la -ldnsapi -liphlpapi /home/vagrant/ruby-gnome2/pango/vendor/local/lib/libpangocairo-1.0.la /home/vagrant/ruby-gnome2/pango/vendor/local/lib/libpangowin32-1.0.la -lusp10 /home/vagrant/ruby-gnome2/pango/vendor/local/lib/libpangoft2-1.0.la /home/vagrant/ruby-gnome2/pango/vendor/local/lib/libharfbuzz.la /home/vagrant/ruby-gnome2/pango/vendor/local/lib/libpango-1.0.la /home/vagrant/ruby-gnome2/glib2/vendor/local/lib/libgthread-2.0.la /home/vagrant/ruby-gnome2/pango/vendor/local/lib/libfribidi.la /home/vagrant/ruby-gnome2/glib2/vendor/local/lib/libgobject-2.0.la /home/vagrant/ruby-gnome2/glib2/vendor/local/lib/libffi.la /home/vagrant/rcairo/vendor/local/lib/libcairo.la -lpthread /home/vagrant/rcairo/vendor/local/lib/libpixman-1.la /home/vagrant/rcairo/vendor/local/lib/libfontconfig.la /home/vagrant/rcairo/vendor/local/lib/libfreetype.la -lgdi32 -lmsimg32 /home/vagrant/rcairo/vendor/local/lib/libpng16.la /home/vagrant/ruby-gnome2/rsvg2/vendor/local/lib/libcroco-0.6.la /home/vagrant/ruby-gnome2/glib2/vendor/local/lib/libglib-2.0.la -lole32 -lwinmm -lshlwapi /home/vagrant/ruby-gnome2/glib2/vendor/local/lib/libpcre.la /home/vagrant/ruby-gnome2/glib2/vendor/local/lib/libintl.la /home/vagrant/ruby-gnome2/glib2/vendor/local/lib/libiconv.la /home/vagrant/rcairo/vendor/local/lib/libxml2.la -lz -lws2_32'
+dependency_libs=' -R/home/vagrant/ruby-gnome2/glib2/vendor/local/lib -L/home/vagrant/ruby-gnome2/glib2/vendor/local/lib -L/home/vagrant/rcairo/vendor/local/lib -L/home/vagrant/ruby-gnome2/rsvg2/vendor/local/lib -L/home/vagrant/ruby-gnome2/pango/vendor/local/lib -L/home/vagrant/ruby-gnome2/gdk_pixbuf2/vendor/local/lib /home/vagrant/ruby-gnome2/gdk_pixbuf2/vendor/local/lib/libgdk_pixbuf-2.0.la /home/vagrant/ruby-gnome2/glib2/vendor/local/lib/libgio-2.0.la /home/vagrant/ruby-gnome2/glib2/vendor/local/lib/libgmodule-2.0.la -ldnsapi -liphlpapi /home/vagrant/ruby-gnome2/pango/vendor/local/lib/libpangocairo-1.0.la /home/vagrant/ruby-gnome2/pango/vendor/local/lib/libpangowin32-1.0.la -lusp10 /home/vagrant/rcairo/vendor/local/lib/libcairo.la -lpthread /home/vagrant/rcairo/vendor/local/lib/libpixman-1.la -lgdi32 -lmsimg32 /home/vagrant/ruby-gnome2/pango/vendor/local/lib/libpangoft2-1.0.la /home/vagrant/ruby-gnome2/pango/vendor/local/lib/libharfbuzz.la /home/vagrant/ruby-gnome2/pango/vendor/local/lib/libpango-1.0.la /home/vagrant/ruby-gnome2/glib2/vendor/local/lib/libgthread-2.0.la /home/vagrant/ruby-gnome2/pango/vendor/local/lib/libfribidi.la /home/vagrant/ruby-gnome2/glib2/vendor/local/lib/libgobject-2.0.la /home/vagrant/ruby-gnome2/glib2/vendor/local/lib/libffi.la /home/vagrant/rcairo/vendor/local/lib/libfontconfig.la /home/vagrant/rcairo/vendor/local/lib/libfreetype.la /home/vagrant/rcairo/vendor/local/lib/libpng16.la /home/vagrant/ruby-gnome2/rsvg2/vendor/local/lib/libcroco-0.6.la /home/vagrant/ruby-gnome2/glib2/vendor/local/lib/libglib-2.0.la -lole32 -lwinmm -lshlwapi /home/vagrant/ruby-gnome2/glib2/vendor/local/lib/libpcre.la /home/vagrant/ruby-gnome2/glib2/vendor/local/lib/libintl.la /home/vagrant/ruby-gnome2/glib2/vendor/local/lib/libiconv.la /home/vagrant/rcairo/vendor/local/lib/libxml2.la -lz -lws2_32'
 
 # Names of additional weak libraries provided by this library
 weak_library_names=''
 
 # Version information for librsvg-2.
-current=42
-age=40
-revision=20
+current=44
+age=42
+revision=3
 
 # Is this an already installed library?
 installed=yes

data/vendor/local/lib/pkgconfig/librsvg-2.0.pc

@@ -8,7 +8,7 @@ css_supported=true
 
 Name: librsvg
 Description: library that renders svg files
-Version: 2.40.20
+Version: 2.42.3
 Requires: glib-2.0 gio-2.0 gdk-pixbuf-2.0 cairo
 Requires.private:
 Libs: -L${libdir} -lrsvg-2 -lm

data/vendor/local/share/doc/librsvg/COMPILING.md

@@ -0,0 +1,266 @@
+Compiling librsvg
+=================
+
+Librsvg uses a mostly normal [autotools] setup, but it has some
+peculiarities due to librsvg's use of a Rust sub-library.  The details
+of how librsvg integrates Cargo and Rust into its autotools setup are
+described in [this blog post][blog], although hopefully you will not
+need to refer to it.
+
+It is perfectly fine to [ask the maintainer][maintainer] if you have
+questions about the Autotools setup; it's a tricky bit of machinery,
+and we are glad to help.
+
+There are generic compilation/installation instructions in the
+[`INSTALL`][install] file, which comes from Autotools.  The following
+explains librsvg's peculiarities.
+
+* [Installing dependencies for building](#installing-dependencies-for-building)
+* [Basic compilation instructions](#basic-compilation-instructions)
+* [Verbosity](#verbosity)
+* [Debug or release builds](#debug-or-release-builds)
+* [Cross-compilation](#cross-compilation)
+* [Building with no network access](#building-with-no-network-access)
+
+# Installing dependencies for building
+
+To compile librsvg, you need the following packages installed.  The
+minimum version is listed here; you may use a newer version instead.
+
+**Compilers:**
+
+* a C compiler and `make` tool; we recommend GNU `make`.
+* rust 1.21
+* cargo
+
+**Mandatory dependencies:**
+
+* Cairo 1.15.4 with PNG support
+* Freetype2 2.8.0
+* Libcroco 0.6.1
+* Gdk-pixbuf 2.20.0
+* GIO 2.24.0
+* GObject-Introspection 0.10.8
+* Libxml2 2.9.0
+* Pango 1.38.0
+
+**Optional dependencies:**
+
+* GTK+ 3.10.0 if you want the `rsvg-view-3` program
+
+The following sections describe how to install these dependencies on
+several systems.
+
+### Debian based systems
+
+As of 2018/Feb/22, librsvg cannot be built in `debian stable` and
+`ubuntu 16.04`, as they have packages that are too old.
+
+**Build dependencies on Debian Testing:**
+
+```sh
+apt-get install -y gcc make rustc cargo \
+automake autoconf libtool gettext itstool \
+libgdk-pixbuf2.0-dev libgirepository1.0-dev \
+gtk-doc-tools git libgtk-3-dev \
+libxml2-dev libcroco3-dev libcairo2-dev libpango1.0-dev
+```
+
+**Build dependencies on Ubuntu 18.04 or newer:**
+
+As of 2018/Feb/22 you will need to install `rustc` and `cargo` with
+[rustup.rs](https://rustup.rs), as the `rustc` package from Ubuntu is
+too old.  Please follow the instructions there to install Rust and Cargo.
+
+```sh
+apt-get install -y gcc make \
+automake autoconf libtool gettext itstool \
+libgdk-pixbuf2.0-dev libgirepository1.0-dev \
+gtk-doc-tools git libgtk-3-dev \
+libxml2-dev libcroco3-dev libcairo2-dev libpango1.0-dev
+```
+
+### Fedora based systems
+
+```sh
+dnf install -y gcc rust rust-std-static cargo make \
+automake autoconf libtool gettext itstool \
+gdk-pixbuf2-devel gobject-introspection-devel \
+gtk-doc git redhat-rpm-config gtk3-devel \
+libxml2-devel libcroco-devel cairo-devel pango-devel
+```
+
+### openSUSE based systems
+
+```sh
+zypper install -y gcc rust rust-std cargo make \
+automake autoconf libtool gettext itstool git \
+gtk-doc gobject-introspection-devel gtk3-devel \
+libxml2-devel libcroco-devel cairo-devel \
+pango-devel gdk-pixbuf-devel
+```
+
+### MacOS systems
+
+Dependencies may be installed using [Homebrew](https://brew.sh) or another
+package manager.
+
+```sh
+brew install cairo gdk-pixbuf glib libcroco pango \
+gobject-introspection rust
+
+export PKG_CONFIG_PATH="`brew --prefix`/lib/pkgconfig:\
+`brew --prefix libffi`/lib/pkgconfig:\
+/usr/lib/pkgconfig"
+export ARCHFLAGS="-arch x86_64"
+```
+
+Note that `PKG_CONFIG_PATH` must be manually set to include Homebrew's libffi,
+as the system libffi is too old but Homebrew does not install it in a public
+location by default.
+
+Currently, cairo 1.15.4 or later must also be installed manually, as the
+Homebrew package is for the older stable release. This may require adding
+it to `PKG_CONFIG_PATH` as well if you do not install it in `/usr/local`.
+
+Setting `ARCHFLAGS` is required if gobject-introspection is using the system
+Python provided by Apple, as on Homebrew.
+
+
+# Basic compilation instructions
+
+If you are compiling a tarball:
+
+```sh
+./configure
+make
+make install
+```
+
+See the [`INSTALL`][install] file for details on options you can pass
+to the `configure` script to select where to install the compiled
+library.
+
+If you are compiling from a git checkout:
+
+```sh
+./autogen.sh
+make
+make install
+```
+
+# Verbosity
+
+By default the compilation process is quiet, and it just tells you
+which files it is compiling.
+
+If you wish to see the full compilation command lines, use "`make V=1`"
+instead of plain "`make`".
+
+# Debug or release builds
+
+Librsvg has code both in C and Rust, and each language has a different
+way of specifying compilation options to select compiler
+optimizations, or whether debug information should be included.
+
+You should set the `CFLAGS` environment variable with compiler flags
+that you want to pass to the C compiler.
+
+## Controlling debug or release mode for Rust
+
+* With a `configure` option: `--enable-debug` or `--disable-debug`
+* With an environment variable: `LIBRSVG_DEBUG=yes` or `LIBRSVG_DEBUG=no`
+
+For the Rust part of librsvg, we have a flag that
+you can pass at `configure` time.  When enabled, the Rust
+sub-library will have debugging information and no compiler
+optimizations.  *This flag is off by default:* if the flag is not
+specified, the Rust sub-library will be built in release mode (no
+debug information, full compiler optimizations).
+
+The rationale is that people who already had scripts in place to build
+binary packages for librsvg, generally from release tarballs, are
+already using conventional machinery to specify C compiler options,
+such as that in RPM specfiles or Debian source packages.  However,
+they may not contemplate Rust sub-libraries and they will certainly
+not want to modify their existing packaging scripts too much.
+
+So, by default, the Rust library builds in **release mode**, to make
+life easier to binary distributions.  Librsvg's build scripts will add
+`--release` to the Cargo command line by default.
+
+Developers can request a debug build of the Rust sub-library by
+passing `--enable-debug` to the `configure` script, or by setting the
+`LIBRSVG_DEBUG=yes` environment variable before calling `configure`.
+This will omit the `--release` option from Cargo, so that it will
+build the Rust sub-library in debug mode.
+
+In case both the environment variable and the command-line option are
+specified, the command-line option overrides the env var.
+
+# Cross-compilation
+
+If you need to cross-compile librsvg, specify the `--host=TRIPLE` to
+the `configure` script as usual with Autotools.  This will cause
+librsvg's build scripts to automatically pass `--target=TRIPLE` to
+`cargo`.
+
+Note, however, that Rust may support different targets than the C
+compiler on your system.  Rust's supported targets can be found in the
+[`rust/src/librustc_back/target`][rust-target-dir] in the Rust
+compiler's source code.
+
+You can check Jorge Aparicio's [guide on cross-compilation for
+Rust][rust-cross] for more details.
+
+## Cross-compiling to a target not supported by Rust out of the box
+
+When building with a target that is not supported out of the box by
+Rust, you have to do this:
+
+1. Create a [target JSON definition file][target-json].
+
+2. Set the environment variable `RUST_TARGET_PATH` to its directory
+   for the `make` command.
+
+Example:
+
+```sh
+cd /my/target/definition
+echo "JSON goes here" > MYMACHINE-VENDOR-OS.json
+cd /source/tree/for/librsvg
+./configure --host=MYMACHINE-VENDOR-OS
+make RUST_TARGET_PATH=/my/target/definition
+```
+
+# Building with no network access
+
+Automated build systems generally avoid network access so that they
+can compile from known-good sources, instead of pulling random updates
+from the net every time.  However, normally Cargo likes to download
+dependencies when it first compiles a Rust project.
+
+We use [`cargo vendor`][cargo-vendor] to ship librsvg release tarballs
+with the source code for Rust dependencies **embedded within the
+tarball**.  If you unpack a librsvg tarball, these sources will appear
+in the `rust/vendor` subdirectory.  If you build librsvg from a
+tarball, instead of git, it should not need to access the network to
+download extra sources at all.
+
+Build systems can use [Cargo's source replacement
+mechanism][cargo-source-replacement] to override the location of the
+source code for the Rust dependencies, for example, in order to patch
+one of the Rust crates that librsvg uses internally.
+
+The source replacement information is in `rust/.cargo/config` in the
+unpacked tarball.  Your build system can patch this file as needed.
+
+[autotools]: https://autotools.io/index.html
+[blog]: https://people.gnome.org/~federico/blog/librsvg-build-infrastructure.html
+[maintainer]: README.md#maintainers
+[install]: INSTALL
+[rust-target-dir]: https://github.com/rust-lang/rust/tree/master/src/librustc_back/target
+[cargo-vendor]: https://crates.io/crates/cargo-vendor
+[cargo-source-replacement]: http://doc.crates.io/source-replacement.html
+[rust-cross]: https://github.com/japaric/rust-cross
+[target-json]: https://github.com/japaric/rust-cross#target-specification-files

data/vendor/local/share/doc/librsvg/CONTRIBUTING.md

@@ -0,0 +1,152 @@
+Contributing to librsvg
+=======================
+
+Thank you for looking in this file!  There are different ways of
+contributing to librsvg, and we appreciate all of them.
+
+* [Source repository](#source-code)
+* [Reporting bugs](#reporting-bugs)
+* [Feature requests](#feature-requests)
+* [Merge requests](#merge-requests)
+
+There is a **code of conduct** for contributors to librsvg; please see the
+file [`code-of-conduct.md`][coc].
+
+## Source repository
+
+Librsvg's main source repository is at gitlab.gnome.org.  You can view
+the web interface here:
+
+https://gitlab.gnome.org/GNOME/librsvg
+
+Development happens in the master branch.  There are also branches for
+stable releases.
+
+Alternatively, you can use the mirror at Github:
+
+https://github.com/GNOME/librsvg
+
+Note that we don't do bug tracking in the Github mirror; see the next
+section.
+
+If you need to publish a branch, feel free to do it at any
+publically-accessible Git hosting service, although gitlab.gnome.org
+makes things easier for the maintainers of librsvg.
+
+## Reporting bugs
+
+Please report bugs at https://gitlab.gnome.org/GNOME/librsvg/issues
+
+If you want to report a rendering bug, or a missing SVG feature,
+please provide an example SVG file as an attachment to your bug
+report.  It really helps if you can minimize the SVG to only the
+elements required to reproduce the bug or see the missing feature, but
+it is not absolutely required.  **Please be careful** of publishing
+SVG images that you don't want other people to see, or images whose
+copyright does not allow redistribution; the bug tracker is a public
+resource and attachments are visible to everyone.
+
+You can also [browse the existing bugs][bugs-browse].
+
+## Feature requests
+
+Librsvg aims to be a small and relatively simple SVG rendering
+library.  Currently we do not plan to support scripting, animation, or
+interactive features like mouse events on SVG elements.
+
+However, we *do* aim go provide good support for SVG's graphical
+features.  Please see the "[reporting bugs](#reporting-bugs)" section for
+information about our bug tracking system; feature requests should be
+directed there.
+
+It is especially helpful if you file bug for a feature request along
+with a sample SVG file.
+
+## Merge requests
+
+### Creating a merge request
+
+You may create a forked version of librsvg in [GNOME's Gitlab
+instance][gitlab], or any other publically-accesible Git hosting
+service.  You can register an account there, or log in with your
+account from other OAuth services.
+
+Note that the maintainers of librsvg only get notified about merge
+requests (or pull requests) if your fork is in
+[gitlab.gnome.org][gitlab].
+
+For technical reasons, the maintainers of librsvg do not get
+automatically notified if you submit a pull request through the GNOME
+mirror in Github.  [Please contact the maintainer][maintainer] directly if you
+have a pull request there or a branch that you would like to
+contribute.
+
+### Test suite
+
+Please make sure that the test suite passes with the changes in your
+branch.  The easiest way to run all the tests is to go to librsvg's
+toplevel directory and run `make check`.  This will run both the small
+unit tests and the black box tests in the `librsvg/tests` directory.
+
+If you need to add new tests (you should, for new features, or for
+things that we weren't testing!), or for additional information on how
+the test suite works, please see the file
+[`tests/README.md`][tests-readme].
+
+### Working on the source
+
+Librvg uses an autotools setup, which is described in detail [in this
+blog post][blog].
+
+If you need to **add a new source file**, you need to do it in the
+toplevel [`Makefile.am`][toplevel-makefile].  *Note that this is for
+both C and Rust sources*, since `make(1)` needs to know when a Rust
+file changed so it can call `cargo` as appropriate.
+
+It is perfectly fine to [ask the maintainer][maintainer] if you have
+questions about the Autotools setup; it's a tricky bit of machinery,
+and we are glad to help.
+
+### Testing changes
+
+The most direct way to test a change is to have an example SVG file
+that exercises the code you want to test.  Then you can rebuild
+librsvg, and run this:
+
+```
+cd /src/librsvg
+libtool --mode=execute ./rsvg-convert -o foo.png foo.svg
+```
+
+Then you can view the resulting `foo.png` image.  Alternatively, you
+can use `./rsvg-view-3` for a quick-and-dirty SVG viewer.
+
+**Please update the test suite** with a suitable example file once you
+have things working (or before even writing code, if you like
+test-driven development), so we can avoid regressions later.  The test
+suite is documented in [`tests/README.md`][tests-readme].
+
+### Testing performance-related changes
+
+You can use the [rsvg-bench] tool to benchmark librsvg.  It lets you
+run a benchmarking program **on an already-installed librsvg
+library**.  For example, you can ask rsvg-bench to render one or more
+SVGs hundreds of times in a row, so you can take accurate timings or
+run a sampling profiler and get enough samples.
+
+**Why is rsvg-bench not integrated in librsvg's sources?**  Because
+rsvg-bench depends on the [rsvg-rs] Rust bindings, and these are
+shipped outside of librsvg.  This requires you to first install
+librsvg, and then compile rsvg-bench.  We aim to make this easier in
+the future.  Of course all help is appreciated!
+
+[coc]: code-of-conduct.md
+[gitlab]: https://gitlab.gnome.org/GNOME/librsvg
+[bugs-browse]: https://gitlab.gnome.org/GNOME/librsvg/issues
+[maintainer]: README.md#maintainers
+[tests-readme]: tests/README.md
+[blog]: https://people.gnome.org/~federico/blog/librsvg-build-infrastructure.html
+[toplevel-makefile]: Makefile.am
+[tests-readme]: tests/README.md
+[rsvg-bench]: https://gitlab.gnome.org/federico/rsvg-bench
+[rsvg-rs]: https://github.com/selaux/rsvg-rs