All of lore.kernel.org
 help / color / mirror / Atom feed
From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] Use of distro_rhel6/7 in refpolicy
Date: Thu, 17 Dec 2015 13:52:29 -0500	[thread overview]
Message-ID: <5673046D.7030404@tresys.com> (raw)
In-Reply-To: <20151217171148.GA26674@x250>

On 12/17/2015 12:11 PM, Dominick Grift wrote:
> On Thu, Dec 17, 2015 at 12:00:14PM -0500, Mike Palmiotto wrote:
>> It appears that the major-version-specific redhat ifdefs were
>> abandoned as of 6624f9cf7a3cdc3deb19ca680f559011a75e5e9f, in favor of
>> generic distro names. Considering the fact that there are some major
>> differences between RHEL6 and RHEL7, I wonder if it would be
>> worthwhile to re-introduce major version numbers. It seems like
>> current efforts have been using 'init_systemd,' but that doesn't seem
>> appropriate for non-systemd policy.
> 
> I suspect "init_systemd" is probably the most accurate identifier you
> one can have in this case.
> 
> systemd is not a RH specific technology even though it is heavily
> influenced by RH. Thus using "distro_rhel7" to indicate systemd seems
> like a bit of a stretch.

Agreed.


>> Is there a particular reason why we wouldn't want to be more specific
>> with the distro ifdefs?

There was a rhel4 distro build option in the past to restore some rules
that were removed in newer distributions due to functional changes.  I'm
not opposed to versioned distro options but am reluctant to accept them
unless their value is clear.


-- 
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com

  parent reply	other threads:[~2015-12-17 18:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-17 17:00 [refpolicy] Use of distro_rhel6/7 in refpolicy Mike Palmiotto
2015-12-17 17:11 ` Dominick Grift
2015-12-17 17:20   ` Mike Palmiotto
2015-12-17 17:22     ` Dominick Grift
2015-12-17 17:41       ` Mike Palmiotto
2015-12-17 18:52   ` Christopher J. PeBenito [this message]
2015-12-17 20:26     ` Mike Palmiotto
2015-12-17 20:51       ` Christopher J. PeBenito
2015-12-17 21:52         ` Mike Palmiotto
2015-12-17 20:56       ` 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=5673046D.7030404@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.