From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH v1] Changes to the miscfiles policy module
Date: Fri, 19 Oct 2012 08:08:45 -0400 [thread overview]
Message-ID: <508142CD.5040706@tresys.com> (raw)
In-Reply-To: <1349794664.30521.31.camel@d30.localdomain>
On 10/09/12 10:57, Dominick Grift wrote:
> On Tue, 2012-10-09 at 10:14 -0400, Christopher J. PeBenito wrote:
>> On 10/05/12 08:56, Dominick Grift wrote:
>>> The file context for /var/cache/man will be handled by mandb
>>>
>>> Change various miscfiles man interfaces to include relevant mandb
>>> interface calls
>>
>> I'm not sure that this is the right way to do. If you have miscfiles and not mandb, then you have a mislabeled /var/cache/man. I looked at your mandb.fc, and the entrypoint looks like a script; what is actually running? makewhatis?
>
> Ok how about we require mandb module by the miscfiles module instead?
>
> I can remove the optional(`')
>
> That way one cannot have the misfiles module without the mandb module
No, modules can't unconditionally depend on modules at higher layers.
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
next prev parent reply other threads:[~2012-10-19 12:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-05 12:56 [refpolicy] [PATCH v1] Changes to the miscfiles policy module Dominick Grift
2012-10-09 14:14 ` Christopher J. PeBenito
2012-10-09 14:18 ` Dominick Grift
2012-10-09 14:20 ` Dominick Grift
2012-10-09 14:38 ` Dominick Grift
2012-10-09 14:57 ` Dominick Grift
2012-10-19 12:08 ` Christopher J. PeBenito [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-10-14 16:31 dominick.grift at gmail.com
2012-10-30 19:27 ` Dominick Grift
2012-10-31 14:43 ` Christopher J. PeBenito
2012-10-31 14:52 ` Dominick Grift
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=508142CD.5040706@tresys.com \
--to=cpebenito@tresys.com \
--cc=refpolicy@oss.tresys.com \
/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 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.