Re: siteinfo for recipes oe-core lacks?

[Mark Hatle <mark.hatle@windriver.com>]

On 7/13/11 8:44 PM, Tom Rini wrote:
> On 07/13/2011 06:20 PM, Mark Hatle wrote:
>> On 7/13/11 5:14 PM, Tom Rini wrote:
>>> Hey all,
>>>
>>> Do we have an opinion on siteinfo for recipes that oe-core lacks?  I
>>> have two easy examples:
>>> - mono: neither meta-oe nor oe-core have a recipe, we have siteinfo
>>> stuff specific to it.  Ignore it? drop it?  update it with what meta-oe has?
>>> - postgresql: meta-oe has it, oe-core lacks it.  Keep in meta-oe only?
>>>
>>
>> For both of them, I'd keep them as local to the recipe as possible.. no recipe,
>> no siteinfo listed.
> 
> Well, I think we're missing the forest for the trees.  But that's not
> really a workable idea since it's sizeof this and that stuff.
> 
> To give you a third example, I've ported this commit over to oe-core:
> http://git.openembedded.org/cgit.cgi/openembedded/commit/?id=bb12cd9c0a757e6ef696d57923821829f00ace79
> 

I think I wasn't clear.  What I meant was that the siteinfo stuff should be as
close to the recipe as possible.  But that doesn't preclude it from being in a
layer specific siteinfo file.

For the samba example, it makes sense to me if we could put these values local
to the recipe -- this assumes nothing else is known to use those configuration
settings.  Once we have multiple packages using the configuration settings they
move up to the layer site file...  once recipes move into the oe-core layer then
the siteinfo moves with them.

Keeping the information as local to recipe as possible helps with maintenance
IMHO.  There is nothing worse then after a few years looking over a siteinfo
file and seeing 100 entries and having no idea if they are still relevant, or
how someone came to specific results.

--Mark