[oe] [PATCH] Epoch support for bitbake (was: Re: RFC: Xorg Version Numbering)

[pHilipp Zabel]

On 1/31/07, Richard Purdie <rpurdie at rpsys.net> wrote:
> Can anyone remember the specifics of the problem with bitbake? I guess
> its easy enough to test and find out...
>
> /me adds looking at this to his todo list...
> (unless anyone beats me to it ;-)

After some discussion on IRC, I came up with the attached patch.
It adds support for a new integer variable PE (package epoch) in the
version comparison code and bitbake cache.
It also changes the code that handles PREFERRED_VERSION to optionally
allow specifying PE (similar to how it is done with PR already).
Especially the provider.py part is just a quick proof of concept. It
always selects
the package with the highest epoch first if the epoch is not
explicitly mentioned
in PREFERRED_VERSION.

So given we have a provider foo with PE="0" (default), PV="1.0",
PR="r0" (1.0-r0)
and a second provider foo with PE="1", PV="1.0", PR="r0" (1:1.0-r0), setting
PREFERRED_VERSION_foo = "0:1.0_r0" will select foo 1.0-r0, setting
PREFERRED_VERSION_foo = "1:1.0_r0" will select foo 1:1.0-r0, and setting
PREFERRED_VERSION_foo = "1.0" will select foo 1:1.0-r0. The last example
is open to discussion. Should an omitted epoch in PREFERRED_VERSION
be considered as PE="0", or should the provider with the greatest PE
be selected?

regards
Philipp
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bitbake-epoch.patch
Type: text/x-patch
Size: 5094 bytes
Desc: not available
URL: <http://lists.openembedded.org/pipermail/openembedded-devel/attachments/20070131/9711a7cd/attachment-0005.bin>