From: Marius Bakke <mbakke@fastmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: Disabling SELinux support in GLib?
Date: Tue, 28 Jan 2020 00:08:06 +0100 [thread overview]
Message-ID: <87zhe8qyzt.fsf@devup.no> (raw)
In-Reply-To: <87wo9ctuf7.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 1323 bytes --]
Ricardo Wurmus <rekado@elephly.net> writes:
> Hi Marius,
>
>> The 'glib' package gained SELinux support back in commit
>> 6c237a2d7bfa3c7be02c069e5c24a2b401a51864. We do not currently support
>> SELinux in Guix System, so I'm not sure if it is worth having it in
>> GLib. Perhaps it can be useful on foreign distributions?
>
> I’m pretty sure that I added it back then because it was needed by
> something else down the line. Unfortunately, I do not recall what that
> may have been.
Right. I haven't tried building anything with SELinux disabled yet.
Arch does not enable SELinux support in GLib, so we can look at how they
tackled the issues that arise.
>> It does not add a lot to the GLib size (~3.8 MiB), but it is a
>> propagated dependency that can be easily avoided.
>
> Can we somehow avoid propagation instead?
The reason I started looking at this was because I want to remove
propagated inputs that are in "Requires.private" in the pkg-config
files, as they should only be necessary when linking statically.
Unfortunately libselinux can only be built statically (AFAICT), so I
suspect most GLib dependents end up embedding libselinux.a, which I did
not account for in the initial size calculation. :-)
(libselinux also fails to cross-compile, but then so does GLib)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
prev parent reply other threads:[~2020-01-27 23:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-27 22:05 Disabling SELinux support in GLib? Marius Bakke
2020-01-27 22:18 ` Ricardo Wurmus
2020-01-27 23:08 ` Marius Bakke [this message]
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=87zhe8qyzt.fsf@devup.no \
--to=mbakke@fastmail.com \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.