From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH] Add Debian location for rtkit-daemon daemon
Date: Mon, 17 Sep 2012 11:24:32 -0400 [thread overview]
Message-ID: <505740B0.4080001@tresys.com> (raw)
In-Reply-To: <20120917172203.7495d085@eldamar.bigon.be>
On 09/17/12 11:22, Laurent Bigonville wrote:
> Le Mon, 17 Sep 2012 11:17:17 -0400,
> "Christopher J. PeBenito" <cpebenito@tresys.com> a ?crit :
>
>> We can always remove the ifdef if Fedora uses that path. But in this
>> case, the fc seems odd to me; why would you put a service's
>> executable in /usr/lib (even as a subdir)?
>
> Debian is not using libexec and puts these files in /usr/lib/*/ instead
To clarify, I wasn't saying the patch should be rejected, but rather that because it seems like a very nontraditional place, I think it would warrant using the ifdef.
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
next prev parent reply other threads:[~2012-09-17 15:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-12 22:14 [refpolicy] [PATCH] Add Debian location for rtkit-daemon daemon Laurent Bigonville
2012-09-13 12:19 ` Dominick Grift
2012-09-13 15:56 ` Daniel J Walsh
2012-09-13 16:06 ` Dominick Grift
[not found] ` <CAPzO=NxQt0cecrjV3r-NYFhPoJrk-wWj37GeC2i8SXRc9vf0Xg@mail.gmail.com>
2012-09-14 15:30 ` Sven Vermeulen
2012-09-15 11:35 ` Laurent Bigonville
2012-09-15 18:08 ` Sven Vermeulen
2012-09-15 18:19 ` Dominick Grift
2012-09-16 19:31 ` Elia Pinto
2012-09-16 20:45 ` Dominick Grift
2012-09-17 15:17 ` Christopher J. PeBenito
2012-09-17 15:22 ` Laurent Bigonville
2012-09-17 15:24 ` Christopher J. PeBenito [this message]
2012-09-17 15:25 ` Daniel J Walsh
2012-09-17 15:30 ` Sven Vermeulen
2012-09-17 15:31 ` Daniel J Walsh
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=505740B0.4080001@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.