Github messages for voidlinux
 help / color / mirror / Atom feed
From: oreo639 <oreo639@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] lcms2: disable plugins for now
Date: Tue, 30 Jan 2024 03:38:09 +0100	[thread overview]
Message-ID: <20240130023809.4423B221F3@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48438@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1885 bytes --]

There is an updated pull request by oreo639 against master on the void-packages repository

https://github.com/oreo639/void-packages lmcs2
https://github.com/void-linux/void-packages/pull/48438

lcms2: disable plugins for now
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **briefly**

Plugins were enabled in https://github.com/void-linux/void-packages/commit/b9b9189c8a7c6f2e8e600958dbc298b7c69c7417
The plugins get linked to applications (`dlopen()` is not used). However they were not added to `common/shlibs` causing packages to link against the plugins but error due to the shlibs not having an associated package.

The plugins don't have a soversion, however, as this is inconsistent between configuring with autoconf vs meson, I assume this is a mistake. As such, disable until the following is addressed: https://github.com/mm2/Little-CMS/issues/432

Fixes building gimp, Krita, libraw, etc.

cc: @sgn 

<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->

<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - aarch64-musl
  - armv7l
  - armv6l-musl
-->


A patch file from https://github.com/void-linux/void-packages/pull/48438.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-lmcs2-48438.patch --]
[-- Type: text/x-diff, Size: 1073 bytes --]

From c8aa91e3f23efdc5c5a6d03b9fd986619b52b610 Mon Sep 17 00:00:00 2001
From: oreo639 <oreo6391@gmail.com>
Date: Mon, 29 Jan 2024 18:28:12 -0800
Subject: [PATCH] lcms2: disable plugins for now

---
 srcpkgs/lcms2/template | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/lcms2/template b/srcpkgs/lcms2/template
index 0116b8698b670..2c74aa4f5ee4d 100644
--- a/srcpkgs/lcms2/template
+++ b/srcpkgs/lcms2/template
@@ -1,7 +1,7 @@
 # Template file for 'lcms2'
 pkgname=lcms2
 version=2.16
-revision=1
+revision=2
 build_style=meson
 configure_args="-Dutils=true -Dsamples=true $(vopt_bool plugins fastfloat) $(vopt_bool plugins threaded)"
 hostmakedepends="pkg-config"
@@ -13,7 +13,7 @@ homepage="https://littlecms.com"
 distfiles="${SOURCEFORGE_SITE}/lcms/lcms2-${version}.tar.gz"
 checksum=d873d34ad8b9b4cea010631f1a6228d2087475e4dc5e763eb81acc23d9d45a51
 build_options="plugins"
-build_options_default="plugins"
+build_options_default=" "
 desc_option_plugins="Build with threaded and fast float plugins (GPL-3.0-or-later)"
 
 post_install() {

  reply	other threads:[~2024-01-30  2:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-30  2:35 [PR PATCH] " oreo639
2024-01-30  2:38 ` oreo639 [this message]
2024-01-30  3:06 ` sgn
2024-01-30  3:16 ` oreo639
2024-01-30  3:35 ` oreo639
2024-01-30  3:38 ` oreo639
2024-01-30  3:59 ` [PR PATCH] [Merged]: " oreo639

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=20240130023809.4423B221F3@inbox.vuxu.org \
    --to=oreo639@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).