all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Matt Wette <matt.wette@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>, "Ricardo Wurmus" <rekado@elephly.net>
Cc: 39172@debbugs.gnu.org
Subject: bug#39172: SElinux guix-daemon.cil file
Date: Tue, 28 Jan 2020 05:45:38 -0800	[thread overview]
Message-ID: <523bc412-7451-3d32-6ab5-854fab4063ff@gmail.com> (raw)
In-Reply-To: <87d0b4fu1m.fsf@gnu.org>

On 1/27/20 1:50 PM, Ludovic Courtès wrote:
> Hello,
>
> Ricardo Wurmus <rekado@elephly.net> skribis:
>
>> Could we also do this in one expression?
>>
>>      (typeattributeset file_type (or guix_profiles_t
>>                                      guix_daemon_conf_t
>>                                      guix_daemon_exec_t
>>                                      guix_daemon_socket_t
>>                                      guix_store_content_t))
>>
>> I also think we need to declare our use of “file_type” first:
>>
>>      (typeattribute file_type)
>>
>> What do you think?
> Matt, does what Ricardo proposes work for you?
>

I can add that and see if it helps.  I am just coming up to speed on this.

There are other changes I may be proposing.
Note that use of

     (block guix_daemon
         ... guix_daemon_conf_t
     )

results in the type guix_daemon.guix_daemon_conf_t.   According to

     https://github.com/SELinuxProject/cil/wiki

the convention is something like the following, with added typealias

      (block guix
        ... daemon_conf
      )

     (typealias guix.daemon_conf guix_daemon_conf_t)

      reply	other threads:[~2020-01-28 13:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-18 15:40 bug#39172: SElinux guix-daemon.cil file Matt Wette
2020-01-20  9:13 ` Ludovic Courtès
2020-01-20 10:35   ` Ricardo Wurmus
2020-01-27 21:50     ` Ludovic Courtès
2020-01-28 13:45       ` Matt Wette [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=523bc412-7451-3d32-6ab5-854fab4063ff@gmail.com \
    --to=matt.wette@gmail.com \
    --cc=39172@debbugs.gnu.org \
    --cc=ludo@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.