Re: any point in a single machine recipe using a machine-specific file?

[Martin Jansa <martin.jansa@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1073 bytes --]

On Fri, Apr 19, 2013 at 09:49:56AM -0400, Robert P. J. Day wrote:
> 
>   using the example i patched earlier, here's the file hierarchy for
> raspberry pi's netbase recipe:
> 
> ./netbase_5.0.bbappend
> ./netbase-5.0
> ./netbase-5.0/raspberrypi
> ./netbase-5.0/raspberrypi/interfaces
> ./netbase-5.0/raspberrypi/hosts
> 
>   i understand the notion of a machine-specific subdirectory for
> files, such as what you'd find under a layer like meta-ti which
> defines multiple machines, so this is understandable for meta-ti:
> 
> .
> ./netbase_5.0.bbappend
> ./netbase-5.0
> ./netbase-5.0/beagleboard
> ./netbase-5.0/beagleboard/interfaces
> 
>   but in the case of the rpi, is there any value in putting the files
> under a machine-named subdirectory? of course it won't hurt, but is
> there any point to it?

Yes, meta-rpi layer can be included when doing builds for different
MACHINEs, raspberrypi subdirectory makes sure that their interfaces,
hosts files are not used accidentaly

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]