1 |
Greetings! |
2 |
|
3 |
I just noticed I sent this email on 17.05.2010 to gentoo-soc-subscribe, |
4 |
so here is resend to correct list! |
5 |
|
6 |
---------------- |
7 |
|
8 |
There is a lot going on already with gsoc2010 projects, I will try to |
9 |
explain more about g-pypi status. At best, I will send email every |
10 |
Monday summarizing past week and plan for the following one. |
11 |
|
12 |
For those unfamiliar with term g-pypi, here is how I would describe it: |
13 |
|
14 |
- cli tool for querying Python Package Index and creating ebuild from it |
15 |
- manages automatically manifests, portage categories and echangelog if |
16 |
requested |
17 |
- at final state it should be able to populate "g-pypi" overlay with |
18 |
successfully built ebuilds |
19 |
|
20 |
Previous week (10-16 May) |
21 |
------------------------- |
22 |
|
23 |
Main goal was to prepare environment and tools for development. |
24 |
|
25 |
Repository, issue tracker: http://bitbucket.org/iElectric/g-pypi2 |
26 |
Hudson CI instance: http://hudson.fubar.si/job/g-pypi2/ |
27 |
Sphinx skeleton documentation: http://docs.fubar.si/gpypi2/ |
28 |
|
29 |
More about each sprint (weekly coding interval) and tickets can be read |
30 |
at http://neurogeek.ath.cx/g-pypi |
31 |
|
32 |
enamer.py (metadata conversion) and portage_util.py (portage lookup |
33 |
information) have already been ported from original g-pypi package. |
34 |
Currently we have almost 100% test coverage for enamer and 0% coverage |
35 |
for portage_utils. Mocker will be used for portage_utils testing, but |
36 |
currently I have to see exactly what functions do we actually still need |
37 |
from the current module. |
38 |
|
39 |
|
40 |
Upcoming week (17-23 May) |
41 |
------------------------- |
42 |
|
43 |
I'm actually on vacations from 18-24 May, with no internet connection |
44 |
(according to current information). Can not promise much, but here is |
45 |
the basic idea what could be done offline during some "fresh air" pauses |
46 |
in Montenegro: |
47 |
|
48 |
* port ebuild.py and cli.py |
49 |
* migrate enamer functions to a class that can be later pluggable (for |
50 |
sake of modularity) |
51 |
* write class that tries to get SRC_URI (currently implementation will |
52 |
query pypi and sourceforge by issuing HEAD HTTP request) |
53 |
* test enamer functions against whole pypi mirror (specially version |
54 |
parsing) |
55 |
|
56 |
|
57 |
Cheers, Domen |