[OE-core] [PATCH 00/45] Move recipes to use Python 3 whenever possible

Alexander Kanavin alexander.kanavin at linux.intel.com
Thu May 26 13:49:33 UTC 2016


On 05/26/2016 04:39 PM, Mark Hatle wrote:

> The interchange format of the newer createrepo is very different then the older
> format the smartpm uses.  Thus they have to be kept in sync.  The new format
> also does not have the extensions we added for the recommended package syntax.
>
> createrepo is very small, and it's not YUM dependent.  It simply reads the
> metadata (via the rpm interface) and dumps out data in an XML format.. then does
> a few more things as well.  So porting the existing one forward shouldn't be
> difficult.  It's just not clear at this point what the best behavior will be to
> do.. port createrepo forward -- or update smartpm to support the newer format
> (with appropriate extensions.)

I still don't understand why introducing yum/dnf as a replacement for 
smartpm should be avoided at all costs. Like smartpm, it's fully written 
in Python, so that theoretically should be less painful that building 
working binaries.

Alex




More information about the Openembedded-core mailing list