From: Russell Coker <russell@coker.com.au>
To: selinux-refpolicy@vger.kernel.org
Subject: Re: obsolete policy
Date: Wed, 27 Jan 2021 00:29:20 +1100 [thread overview]
Message-ID: <2834968.yUVx8FsqrH@liv> (raw)
In-Reply-To: <2087042.fIsVSkRV3x@liv>
On Tuesday, 26 January 2021 10:28:34 PM AEDT Russell Coker wrote:
> For future reference I think we should we make it standard procedure to
> include the upstream URL for software related to a module in any case that
> it's non-obvious. I could have saved at least an hour if there was a list
> of upstream URLs to check.
This was a badly written paragraph.
We should make it mandatory to include the upstream URL in the policy source
so that future maintainers know where to go to find out if it's still
maintained and to find out any other information that may be necessary. For
some things we don't really need it (like Apache and ssh for example), but
even then it wouldn't do any harm and consistency is good when it only costs a
few bytes in the source tree.
Also my previous message wasn't a list of all the modules that might be
removed. There were a bunch that were Red Hat things with an unclear status
and it was easier to just disable them for the Debian build and let someone
else worry about what Red Hat is doing.
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
next prev parent reply other threads:[~2021-01-26 13:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-26 11:28 obsolete policy Russell Coker
2021-01-26 13:29 ` Russell Coker [this message]
2021-02-16 14:37 ` Chris PeBenito
2021-03-05 1:30 ` Russell Coker
2021-03-06 18:54 ` Chris PeBenito
2021-03-06 19:57 ` Sugar, David
[not found] ` <BLAPR15MB37648F5B6947DB93197727DEC2959@BLAPR15MB3764.namprd15.prod.outlook.com>
2021-03-06 23:11 ` Russell Coker
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=2834968.yUVx8FsqrH@liv \
--to=russell@coker.com.au \
--cc=selinux-refpolicy@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).