| 1 |
On 05/24/2012 01:19 PM, Mike Frysinger wrote: |
| 2 |
> On Thursday 24 May 2012 16:12:35 Kent Fredric wrote: |
| 3 |
>> Were it me, I'd have a tool that scrapes the eclass files's |
| 4 |
>> documentation and emits a .json file which repoman can then optionally |
| 5 |
>> use for consistency checks. |
| 6 |
> |
| 7 |
> python provides its own pickling system. no need to add yet another layer. |
| 8 |
|
| 9 |
Python's json module is similar to the pickly module, so you might just |
| 10 |
use that instead. For example, I've converted /var/cache/edb/mtimedb |
| 11 |
from pickle to json: |
| 12 |
|
| 13 |
http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=848da97a64b2d3d13c3fbc794c57dae714009854 |
| 14 |
|
| 15 |
>> Mostly because I don't like the idea of repoman re-probing all the |
| 16 |
>> eclasses every time you check an ebuild |
| 17 |
> |
| 18 |
> caching of data most likely will be done (the decision will be data driven), |
| 19 |
> but that's independent of the underlying behavioral question. |
| 20 |
|
| 21 |
I expect that reading and validating the cache is probably not going to |
| 22 |
be much faster than just parsing the eclasses over again. |
| 23 |
-- |
| 24 |
Thanks, |
| 25 |
Zac |
Archives