From: oreo639 <oreo639@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: lcms2: disable plugins for now
Date: Tue, 30 Jan 2024 04:35:03 +0100 [thread overview]
Message-ID: <20240130033503.91BE6240B6@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: 393 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/pull/48438#issuecomment-1915999294
Comment:
> Not sure if it would work when we split the plugins into subpackages?
imo, probably best to wait for upstream's response regarding soversions before packaging them. (also they get added to the `lcms2.pc` file, so I'm not sure how that would work)
next prev parent reply other threads:[~2024-01-30 3:35 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 ` [PR PATCH] [Updated] " oreo639
2024-01-30 3:06 ` sgn
2024-01-30 3:16 ` oreo639
2024-01-30 3:35 ` oreo639 [this message]
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=20240130033503.91BE6240B6@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).