[OE-core] Package recipes change proposal (system-wide) - name wise

[Chris Larson]

On Wed, Jul 25, 2012 at 3:09 AM, Paul Eggleton
<paul.eggleton at linux.intel.com> wrote:
> On Wednesday 25 July 2012 07:23:31 Iorga, Cristian wrote:
>> For me, having the version number contained in the name of package recipe is
>> a little bit puzzling. For example: libpcre/libpcre_8.31.bb
>>
>> Is there a solid technical reason to not have it like this?
>>
>> libpcre/libpcre.bb
>> and inside the recipe to have a PV variable defined:
>> PV="8.31"
>
> The benefit of having PV in the recipe file name is that you can then easily
> have different recipes for different versions of the same piece of software,
> which is particularly useful when those different versions may need to be built
> slightly differently.

It's worth noting that that can still be done by leveraging
BBVERSIONS. Not that I'm advocating that approach necessarily, but
noting that it can still be done without using multiple recipes with
version in the filename.
-- 
Christopher Larson