From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [RFC] xfce4-4.16
Date: Thu, 24 Dec 2020 01:00:54 +0100 [thread overview]
Message-ID: <20201224000054.L7yRZjX0EF8ex8xOeRMNvRw4EluAhwnqSykU7sHkZLA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27367@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 920 bytes --]
New comment by sgn on void-packages repository
https://github.com/void-linux/void-packages/pull/27367#issuecomment-750601830
Comment:
On 2020-12-23 08:07:16-0800, Peter Bui <notifications@github.com> wrote:
> @sgn Did you need me to do anything regarding the plugins?
Probably needs to update xfce4-mailwatch-plugin, I think.
I'll remove other plugins, they're very old, and not updated to new
shlib. I may see if I can patch those plugins to use new ABI, sometime
later.
exo provides both shlib for a long time for transitioning, if they
don't act, I think it's safely remove them.
> how did you get a list of broken plugins (for future reference)?
Mainly because I'm lazy and I have xfce4-plugins installed, which
pulls all of those plugins.
You can see the dependencies list with xrevshlib <pkgname>
Anyway, there's some entry for old SONAME is common/shlib,
Some cleanup will be welcome.
Thanks,
--
Danh
next prev parent reply other threads:[~2020-12-24 0:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-23 2:23 [PR PATCH] " pbui
2020-12-23 11:49 ` marmeladema
2020-12-23 13:43 ` pbui
2020-12-23 13:48 ` pbui
2020-12-23 13:57 ` ericonr
2020-12-23 14:17 ` [PR PATCH] [Updated] " pbui
2020-12-23 14:41 ` pbui
2020-12-23 14:46 ` sgn
2020-12-23 15:44 ` pbui
2020-12-23 16:07 ` pbui
2020-12-24 0:00 ` sgn [this message]
2020-12-24 0:06 ` sgn
2020-12-26 10:13 ` marmeladema
2020-12-26 11:29 ` sgn
2020-12-26 13:43 ` xfce4-4.16 pbui
2020-12-27 1:58 ` xfce4-4.16 sgn
2020-12-27 14:04 ` [PR PATCH] [Merged]: xfce4-4.16 sgn
2020-12-27 15:08 ` xfce4-4.16 sgn
2020-12-27 15:31 ` xfce4-4.16 sgn
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=20201224000054.L7yRZjX0EF8ex8xOeRMNvRw4EluAhwnqSykU7sHkZLA@z \
--to=sgn@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).