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

[Bruce Ashfield]

On Wed, Jul 25, 2012 at 6: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.

And an example would be the three linux-yocto kernel versions. We'd have
to break them out into separate layers if the version wasn't in the filename.

That being said, the linux-yocto-dev recipe doesn't have a version in it's name
for the same reason, it's simpler to keep it moving forward constantly without
the version in the name.

.. just chiming in from the kernel point of view :)

Cheers,

Bruce

>
> Cheers,
> Paul
>
> --
>
> Paul Eggleton
> Intel Open Source Technology Centre
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core at lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"