From: "Andrew Savchenko" <bircoph@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-text/xpdf/
Date: Sat, 20 Jul 2024 21:12:41 +0000 (UTC) [thread overview]
Message-ID: <1721509929.8638b4d7b8c48f05bc09f5d3bee812d857269bc1.bircoph@gentoo> (raw)
commit: 8638b4d7b8c48f05bc09f5d3bee812d857269bc1
Author: Andrew Savchenko <bircoph <AT> gentoo <DOT> org>
AuthorDate: Sat Jul 20 20:54:01 2024 +0000
Commit: Andrew Savchenko <bircoph <AT> gentoo <DOT> org>
CommitDate: Sat Jul 20 21:12:09 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8638b4d7
app-text/xpdf: update metadata
We're using rsvg-convert instead of inkscape to generate png's now.
Reflect this in the USE=icons flag description.
Signed-off-by: Andrew Savchenko <bircoph <AT> gentoo.org>
app-text/xpdf/metadata.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/app-text/xpdf/metadata.xml b/app-text/xpdf/metadata.xml
index 77412381d44b..7c2232eb3027 100644
--- a/app-text/xpdf/metadata.xml
+++ b/app-text/xpdf/metadata.xml
@@ -8,7 +8,7 @@
<use>
<flag name="cmyk">Include support for CMYK rasterization</flag>
<flag name="i18n">Enable support non-UTF8 national charsets</flag>
- <flag name="icons">Generate desktop PNG icons using <pkg>media-gfx/inkscape</pkg></flag>
+ <flag name="icons">Generate desktop PNG icons using rsvg-convert from <pkg>gnome-base/librsvg</pkg></flag>
<flag name="libpaper">Use <pkg>app-text/libpaper</pkg> to get paper preferences</flag>
<flag name="metric">Use A4 instead of US Letter paper size by default for PostScript output. This option has effect only if libpaper USE flag is disabled</flag>
<flag name="opi">Include support for OPI (Open Prepress Interface) comments</flag>
next reply other threads:[~2024-07-20 21:12 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-20 21:12 Andrew Savchenko [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-07-25 8:22 [gentoo-commits] repo/gentoo:master commit in: app-text/xpdf/ Petr Vaněk
2025-04-21 8:05 Andreas Sturmlechner
2024-08-20 18:05 Sam James
2024-08-20 18:05 Sam James
2024-07-21 19:37 Andrew Savchenko
2024-07-21 0:32 Sam James
2024-07-20 22:46 Sam James
2024-07-20 16:57 Andrew Savchenko
2024-07-20 16:57 Andrew Savchenko
2024-07-20 16:38 Andrew Savchenko
2023-11-16 15:11 Florian Schmaus
2022-09-15 13:20 Sam James
2022-07-26 15:32 Andrew Savchenko
2022-07-26 15:02 Andrew Savchenko
2022-07-03 10:52 Agostino Sarubbo
2022-07-03 10:48 Agostino Sarubbo
2022-05-15 13:58 Andrew Savchenko
2021-02-09 9:47 Sam James
2021-02-08 17:26 Sam James
2021-01-30 9:52 Andrew Savchenko
2021-01-30 9:52 Andrew Savchenko
2021-01-30 9:52 Andrew Savchenko
2020-11-09 18:05 Andrew Savchenko
2020-09-19 15:40 Andrew Savchenko
2020-09-19 10:21 Andrew Savchenko
2020-04-30 20:19 Andrew Savchenko
2020-04-30 16:00 Agostino Sarubbo
2020-04-30 15:56 Agostino Sarubbo
2020-04-30 9:01 Andrew Savchenko
2020-04-30 8:41 Andrew Savchenko
2020-04-05 8:45 Andrew Savchenko
2020-03-02 22:33 Andrew Savchenko
2020-03-02 12:32 Agostino Sarubbo
2020-03-02 9:24 Agostino Sarubbo
2019-10-28 7:41 Agostino Sarubbo
2019-10-27 23:20 Thomas Deutschmann
2019-10-27 9:29 Andrew Savchenko
2019-10-23 14:36 Andrew Savchenko
2019-03-21 11:00 Andrew Savchenko
2019-03-21 11:00 Andrew Savchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1721509929.8638b4d7b8c48f05bc09f5d3bee812d857269bc1.bircoph@gentoo \
--to=bircoph@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox