From: Roland Hieber <rhi@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Michael Olbrich <m.olbrich@pengutronix.de>,
Roland Hieber <rhi@pengutronix.de>
Subject: [ptxdist] [PATCH] libcroco: move to staging
Date: Fri, 29 May 2020 12:23:52 +0200 [thread overview]
Message-ID: <20200529102352.18872-1-rhi@pengutronix.de> (raw)
Suggested-by: Michael Olbrich <m.olbrich@pengutronix.de>
Signed-off-by: Roland Hieber <rhi@pengutronix.de>
---
rules/libcroco.in | 9 ++++++++-
rules/librsvg.in | 1 +
2 files changed, 9 insertions(+), 1 deletion(-)
diff --git a/rules/libcroco.in b/rules/libcroco.in
index ab709be2f1e0..4f5af324e634 100644
--- a/rules/libcroco.in
+++ b/rules/libcroco.in
@@ -1,4 +1,6 @@
-## SECTION=multimedia_gtk
+## SECTION=staging
+### old section:
+### SECTION=multimedia_gtk
menuconfig LIBCROCO
tristate
@@ -32,6 +34,11 @@ menuconfig LIBCROCO
Note that the xml manipulation toolkit used by the libcroco
selection engine at the moment is libxml2.
+ STAGING: remove in PTXdist 2021.05.0
+
+ Old version that needs to be updated, and license is unclear
+ (headers say LGPL-2.1-or-later, COPYING contains LGPL-2.0)
+
if LIBCROCO
config LIBCROCO_CHECKS
diff --git a/rules/librsvg.in b/rules/librsvg.in
index 3a149ef9c110..461dbaf95609 100644
--- a/rules/librsvg.in
+++ b/rules/librsvg.in
@@ -31,6 +31,7 @@ config LIBRSVG_SVGZ
config LIBRSVG_CROCO
bool
+ depends on STAGING
prompt "libcroco support"
help
Libcroco is a general CSS parsing and manipulation library.
--
2.26.2
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
next reply other threads:[~2020-05-29 10:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 10:23 Roland Hieber [this message]
2020-06-05 5:59 ` [ptxdist] [APPLIED] " Michael Olbrich
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=20200529102352.18872-1-rhi@pengutronix.de \
--to=rhi@pengutronix.de \
--cc=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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