From: Marius Bakke <marius@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>, "Daniel Brooks" <db48x@db48x.net>
Cc: 44649-done@debbugs.gnu.org
Subject: bug#44649: 1.2.0rc0 tarball includes guix-daemon.cil.in
Date: Sun, 15 Nov 2020 23:26:54 +0100 [thread overview]
Message-ID: <87tutq9ryp.fsf@gnu.org> (raw)
In-Reply-To: <87361a8jbc.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 793 bytes --]
Ludovic Courtès <ludo@gnu.org> writes:
> Hi,
>
> Daniel Brooks <db48x@db48x.net> skribis:
>
>> It should instead include the guix-daemon.cil file which was built from
>> it. The .in file has unsubstituted variabels in it which make it useless
>> as an SELinux policy.
>
> Yes, but running “./configure” gives you the ‘etc/guix-daemon.cil’ for
> your configuration. What’s wrong with that?
>
> Marius: common practice is to not include instantiated templates; we
> wouldn’t use templates in the first place if contents were always the
> same. :-)
Yes indeed; somehow I thought the bootstrapped tarball also had run
"configure" with the common options, but obviously that's incorrect.
Closing this bug, as there is no reason to special-case this one file.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 507 bytes --]
prev parent reply other threads:[~2020-11-15 22:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-15 0:51 bug#44649: 1.2.0rc0 tarball includes guix-daemon.cil.in Daniel Brooks
2020-11-15 14:56 ` Marius Bakke
2020-11-15 15:08 ` Daniel Brooks
2020-11-15 21:02 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-11-15 20:19 ` Ludovic Courtès
2020-11-15 21:24 ` Daniel Brooks
2020-11-16 8:12 ` Ludovic Courtès
2020-11-16 12:12 ` Daniel Brooks
2020-11-16 12:53 ` Ludovic Courtès
2020-11-16 13:15 ` Daniel Brooks
2020-11-16 16:15 ` Ludovic Courtès
2020-11-15 22:26 ` 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=87tutq9ryp.fsf@gnu.org \
--to=marius@gnu.org \
--cc=44649-done@debbugs.gnu.org \
--cc=db48x@db48x.net \
--cc=ludo@gnu.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.
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.