aports/community/librsvg/rsvg-h-dont-use-comments-in-comments.patch
Kevin Daudt 44a1afadce community/librsvg: fix comments in rsvg.h
Patch from https://gitlab.gnome.org/GNOME/librsvg/-/merge_requests/688

Causes build failures:

> error: "/*" within comment [-Werror=comment]
2022-04-16 20:26:37 +00:00

32 lines
1.2 KiB
Diff

From d158d111f4b4d539a1f586bf42825c4759386fd4 Mon Sep 17 00:00:00 2001
From: Federico Mena Quintero <federico@gnome.org>
Date: Wed, 6 Apr 2022 13:30:40 -0500
Subject: [PATCH] (#856): Don't use /* as part of the text in C documentation
comments
Compilers don't like it!
Fixes https://gitlab.gnome.org/GNOME/librsvg/-/issues/856
Part-of: <https://gitlab.gnome.org/GNOME/librsvg/-/merge_requests/688>
---
include/librsvg/rsvg.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/librsvg/rsvg.h b/include/librsvg/rsvg.h
index 5a5c97c81..964002354 100644
--- a/include/librsvg/rsvg.h
+++ b/include/librsvg/rsvg.h
@@ -122,7 +122,7 @@ GType rsvg_error_get_type (void);
* if the base file is `/foo/bar/baz.svg`, then librsvg will
* only try to load referenced files (from SVG's
* `<image>` element, for example, or from content
- * included through XML entities) if those files are in `/foo/bar/*` or in `/foo/bar/*\/.../*`.
+ * included through XML entities) if those files are in `/foo/bar/<anything>` or in `/foo/bar/<anything>\/.../<anything>`.
* This is so that malicious SVG files cannot include files that are in a directory above.
*
* The full set of rules for deciding which URLs may be loaded is as follows;
--
GitLab