Received-SPF: pass (google.com: domain of selinux-refpolicy-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Subject: Re: obsolete policy
To:     Russell Coker <russell@coker.com.au>,
        selinux-refpolicy@vger.kernel.org
References: <2087042.fIsVSkRV3x@liv>
From:   Chris PeBenito <pebenito@ieee.org>
Message-ID: <979708e2-2cab-37a4-bf17-60ee0a15af1b@ieee.org>
Date:   Tue, 16 Feb 2021 09:37:08 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
 Thunderbird/78.7.0
MIME-Version: 1.0
In-Reply-To: <2087042.fIsVSkRV3x@liv>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 1/26/21 6:28 AM, Russell Coker wrote:
> Below is the list of policy modules which seem to be obsolete.
> 
> 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.

I think it would be useful, but I also wonder how useful it will be over time 
since projects move from time to time to different providers, github, gitlab, 
bitbucket, etc.

I'd list this as something that should be there but is not required.


-- 
Chris PeBenito