Florian Festi wrote:
Hi!

This is something that annoys me for quite a while. But it was clear to me that it was not fixable in ther past. So now is time to speak up:

What about normalizing the PRCO data to a sane format. There is a wild mixture of integers, comparator signs, two letter abbreviations and None objects used as flags and a continuous conversion between version strings and version tuples.

Even worse is that most functions work only with a part of the combinations and the data formats have to be converted at random points within the source code.

I don't have a complete battle plan yet but encapsulating the two letter flags into the sqlitedb and may be kill the None flags sounds like a good first step to me. We could also make .get(Proides|Requires|...) accept string versions. But it might also be worth converting every version to a tuple right at the beginning.

Comments? Opinions? Patches?

Florian
_______________________________________________
Yum-devel mailing list
[email protected]
https://lists.dulug.duke.edu/mailman/listinfo/yum-devel

+1

Tim
_______________________________________________
Yum-devel mailing list
[email protected]
https://lists.dulug.duke.edu/mailman/listinfo/yum-devel

Reply via email to