From: dominick.grift@gmail.com (Dominick Grift)
Date: Wed, 08 Aug 2012 15:46:10 +0200
Subject: [refpolicy] [PATCH] oidentd fixes
In-Reply-To: <502268AD.8080109@tresys.com>
References: <1344365757-12896-1-git-send-email-dominick.grift@gmail.com>
	<50226587.5010507@tresys.com> <502268AD.8080109@tresys.com>
Message-ID: <1344433570.2306.38.camel@d30.localdomain>
To: refpolicy@oss.tresys.com
List-Id: refpolicy.oss.tresys.com



On Wed, 2012-08-08 at 09:25 -0400, Christopher J. PeBenito wrote:
> On 08/08/12 09:11, Christopher J. PeBenito wrote:
> > On 08/07/12 14:55, Dominick Grift wrote:
> >> remove oidentd_read_user_content because interfaces aren' for internal
> >> usage
> > 
> > That's not actually a refpolicy rule.
>  
> To complete the thought, its fine to use an interface internally.  However, its preferred that you not create an interface only to use it internally unless its a complicated concept you're trying to abstract (e.g. portage_compile_domain()).
> 

And that is actually the case here. The oidentd_read_user_content() is
trivial and is only used internally.