Daniel Brooks skribis:
> Ludovic Courtès writes:
>
Good point! The installed ‘guix’ has that file under
share/selinux/guix-daemon.cil, so perhaps the script could copy it from
there?
>>>
>>> It only has it if you run configure first.
>>
>> “The installed ‘guix’” here refers to
Ludovic Courtès writes:
>>> Good point! The installed ‘guix’ has that file under
>>> share/selinux/guix-daemon.cil, so perhaps the script could copy it from
>>> there?
>>
>> It only has it if you run configure first.
>
> “The installed ‘guix’” here refers to the one
>
Daniel Brooks skribis:
> Ludovic Courtès writes:
>
>> Good point! The installed ‘guix’ has that file under
>> share/selinux/guix-daemon.cil, so perhaps the script could copy it from
>> there?
>
> It only has it if you run configure first.
“The installed ‘guix’” here refers to the one
Ludovic Courtès writes:
> Good point! The installed ‘guix’ has that file under
> share/selinux/guix-daemon.cil, so perhaps the script could copy it from
> there?
It only has it if you run configure first.
db48x
Hi Daniel,
Daniel Brooks skribis:
> Ludovic Courtès writes:
>
>> 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
Ludovic Courtès writes:
> Hi,
>
> Daniel Brooks 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
Ludovic Courtès writes:
> 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.
Daniel Brooks 写道：
Marius Bakke writes:
Actually I think both should be included. The processed file
will work
for 99% of users, and the template is needed for the 1% that
use a
different store directory.
Fair enough.
Is a pre-generated .cil file required to run ./configure at all on
Hi,
Daniel Brooks 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.
Marius Bakke writes:
> Actually I think both should be included. The processed file will work
> for 99% of users, and the template is needed for the 1% that use a
> different store directory.
Fair enough.
Daniel Brooks writes:
> 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.
Actually I think both should be included. The processed file will work
for 99% of users, and the
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.
12 matches
Mail list logo
