From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: Xfce switch to python3
Date: Mon, 20 Jan 2020 15:14:50 +0100 [thread overview]
Message-ID: <20200120141450.xJTXK_BddB3xgBuSOpq5tNrx1OfUw1PPfXILw5-L5CQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-17766@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1265 bytes --]
New comment by sgn on void-packages repository
https://github.com/void-linux/void-packages/pull/17766#issuecomment-576292678
Comment:
On 2020-01-20 05:26:08-0800, Daniel Kolesa <notifications@github.com> wrote:
> Hm, actually, this may be wrong. I'm looking at how other
> distributions do it, and they pretty much all put the modules in
> `libgladeui`; seems like these modules may be used at runtime by
> GLADE-using applications.
Hm, I'm not a heavy user of xfce to conform this.
I mostly set it up for my sister.
From my limited time with xfce, libgladeui works fine without those
modules.
However, Arch disagree with your assertment.
They ship all those modules with glade, see:
https://www.archlinux.org/packages/extra/x86_64/glade/files/
and, the usr/lib/libglade-2.0.so with libgladeui, see:
https://www.archlinux.org/packages/extra/x86_64/libglade/files/
> Which means, the right way would be to move the modules into the
> `libgladeui` package, as well as the python dependencies.
>
> Interestingly, none of them seem to split the modules into subpackages...
I splited those submodules since webkit2gtk dependencies looks too big
to be installed.
However, consider glade is mostly a development package,
I think we can merge it back.
--
Danh
next prev parent reply other threads:[~2020-01-20 14:14 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-25 2:36 [PR PATCH] " voidlinux-github
2019-12-25 8:02 ` [PR PATCH] [Updated] " voidlinux-github
2019-12-25 16:01 ` voidlinux-github
2019-12-25 21:18 ` voidlinux-github
2019-12-26 13:27 ` voidlinux-github
2019-12-26 13:27 ` [PR PATCH] [Updated] " voidlinux-github
2019-12-26 14:23 ` voidlinux-github
2019-12-26 14:40 ` voidlinux-github
2019-12-26 14:42 ` voidlinux-github
2019-12-27 13:01 ` [PR PATCH] [Updated] " voidlinux-github
2020-01-01 6:59 ` voidlinux-github
2020-01-02 12:50 ` voidlinux-github
2020-01-06 23:53 ` voidlinux-github
2020-01-07 0:06 ` voidlinux-github
2020-01-07 14:04 ` voidlinux-github
2020-01-11 2:41 ` voidlinux-github
2020-01-18 10:07 ` voidlinux-github
2020-01-18 10:40 ` voidlinux-github
2020-01-18 11:16 ` voidlinux-github
2020-01-18 14:03 ` voidlinux-github
2020-01-18 23:47 ` [PR PATCH] [Updated] " voidlinux-github
2020-01-18 23:48 ` voidlinux-github
2020-01-18 23:58 ` [PR PATCH] [Updated] " voidlinux-github
2020-01-19 15:00 ` voidlinux-github
2020-01-19 15:00 ` voidlinux-github
2020-01-20 3:06 ` voidlinux-github
2020-01-20 3:09 ` voidlinux-github
2020-01-20 13:26 ` voidlinux-github
2020-01-20 13:36 ` voidlinux-github
2020-01-20 14:14 ` voidlinux-github [this message]
2020-01-20 14:26 ` voidlinux-github
2020-01-20 14:39 ` [PR PATCH] [Updated] " voidlinux-github
2020-01-20 14:45 ` voidlinux-github
2020-01-20 14:45 ` voidlinux-github
2020-01-20 14:55 ` voidlinux-github
2020-01-20 15:04 ` voidlinux-github
2020-01-20 15:04 ` voidlinux-github
2020-01-20 15:06 ` voidlinux-github
2020-01-20 15:10 ` [PR PATCH] [Updated] " voidlinux-github
2020-01-20 15:27 ` voidlinux-github
2020-01-20 15:32 ` voidlinux-github
2020-01-21 4:58 ` voidlinux-github
2020-01-21 4:59 ` [PR PATCH] [Updated] " voidlinux-github
2020-01-21 5:03 ` voidlinux-github
2020-01-21 5:09 ` voidlinux-github
2020-01-22 3:59 ` voidlinux-github
2020-01-22 4:01 ` voidlinux-github
2020-01-22 4:04 ` voidlinux-github
2020-01-30 2:35 ` voidlinux-github
2020-01-30 12:22 ` voidlinux-github
2020-02-03 2:47 ` [PR PATCH] [Updated] " voidlinux-github
2020-02-03 2:47 ` voidlinux-github
2020-02-03 2:48 ` voidlinux-github
2020-02-03 2:48 ` voidlinux-github
2020-02-03 10:30 ` voidlinux-github
2020-02-03 10:32 ` voidlinux-github
2020-02-03 10:33 ` voidlinux-github
2020-02-03 13:09 ` voidlinux-github
2020-02-03 13:14 ` [PR PATCH] [Updated] " voidlinux-github
2020-02-04 1:08 ` voidlinux-github
2020-02-04 2:59 ` voidlinux-github
2020-02-04 7:35 ` voidlinux-github
2020-02-04 7:59 ` voidlinux-github
2020-02-04 12:40 ` voidlinux-github
2020-02-04 13:17 ` voidlinux-github
2020-02-04 20:11 ` voidlinux-github
2020-02-05 15:01 ` [PR PATCH] [Closed]: " voidlinux-github
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=20200120141450.xJTXK_BddB3xgBuSOpq5tNrx1OfUw1PPfXILw5-L5CQ@z \
--to=voidlinux-github@inbox.vuxu.org \
--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).