From: dac.override@gmail.com (Dominick Grift)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] Use of distro_rhel6/7 in refpolicy
Date: Thu, 17 Dec 2015 18:11:50 +0100 [thread overview]
Message-ID: <20151217171148.GA26674@x250> (raw)
In-Reply-To: <CAMN686GNnTThWuMvN-LTnLUjg9L+OizyQSgj-EF-QmeHpzFPaQ@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
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.
>
> Is there a particular reason why we wouldn't want to be more specific
> with the distro ifdefs?
>
> Respectfully,
> --Mike
> _______________________________________________
> refpolicy mailing list
> refpolicy at oss.tresys.com
> http://oss.tresys.com/mailman/listinfo/refpolicy
- --
02DFF788
4D30 903A 1CF3 B756 FB48 1514 3148 83A2 02DF F788
https://sks-keyservers.net/pks/lookup?op=get&search=0x314883A202DFF788
Dominick Grift
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQGcBAEBCgAGBQJWcuzQAAoJENAR6kfG5xmcYGcL/3V0kK53j6JmKwviBix17hpw
dgWYJYcuIw8gWcdG+ClAmt+mspPoxo324lvLvBsYOLK2c3KD/O4gDtezr+snLE89
W/1pmZNW51Ved0muefZW892+aP6fYbYD9vjCXe19IlcQGiqXIZWad0J+qrlt2xbe
rvHXpOTZ+a6HI7Mqkqmc2Gp4NG1tx1YbrgdOX1mNb0O5o6FAl6a4d3HwcWbej9R6
KoOXm/EmzQB/JS68FxaCKJ8LgIrE4p0RhdXCXAoKNyGQSPpoMv6rpjJFUtkJPqcu
0+vkzUmIAPDXLhCQwGErRJ/Q/QHG14HLXB8/Xdj2y8zjHria2jKZl0iyI6gCl9/n
QYSEY84/+dH72ROS9MJZMA6XBUUQTkBD/f2kQ9bQUJDYJREtQpvPisIW4//6Q3+G
jzhURFK/csiOHibLuw9UR7ELfM3jg7IhT4Gei8EBCF116Kgoz6KabDh30LZfgObF
Mqhk3P5UdM8diZNzqgz6br5mNWlfZkaGCya0EoOnJw==
=xOGX
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2015-12-17 17:11 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 [this message]
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
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=20151217171148.GA26674@x250 \
--to=dac.override@gmail.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.