| 1 |
----------------------------------------------------------------------- |
| 2 |
Plaintext version: |
| 3 |
|
| 4 |
Greetings, following is the weekly update for gpypi2 project. It's main |
| 5 |
purpose is to generate ebuilds from Python Package Index. Quick links to |
| 6 |
project info: |
| 7 |
|
| 8 |
Repository, issue tracker: http://bitbucket.org/iElectric/g-pypi2 |
| 9 |
Hudson CI instance: http://hudson.fubar.si/job/g-pypi2/ |
| 10 |
Sphinx documentation generated by hudson on each |
| 11 |
commit:http://docs.fubar.si/gpypi2/ |
| 12 |
|
| 13 |
GPyPi knows about metadata.xml, ChangeLog and Manifest! |
| 14 |
|
| 15 |
====================================================================== |
| 16 |
Previous week (2nd - 9th August)Task: metadata, echangelog and manifest |
| 17 |
generation |
| 18 |
====================================================================== |
| 19 |
|
| 20 |
---------------------------------------------------------------------- |
| 21 |
>Task: In the last week of implementing features I will add support for |
| 22 |
Gentoo developers workflow. |
| 23 |
|
| 24 |
Done. Implementation is in gpypi2/workflow.py. One issue though: |
| 25 |
echangelog has no idea how to add files to SCM, will have to find |
| 26 |
another abstraction tool for that. |
| 27 |
---------------------------------------------------------------------- |
| 28 |
> Task: Atomic actions |
| 29 |
> Currently if anything fails in the process, data will lay around the |
| 30 |
filesytem. |
| 31 |
> I'll implement most basic cleanup (rollback) on failures. |
| 32 |
|
| 33 |
I haven't touched this one, mostly because I don't have a good idea how |
| 34 |
to handle tracking of files. |
| 35 |
---------------------------------------------------------------------- |
| 36 |
> Task: Exceptions |
| 37 |
> Code currently uses a bit of exceptions and a bit of log.error. |
| 38 |
> I'll make that a bit structured and also document what exceptions are |
| 39 |
raised in functions |
| 40 |
|
| 41 |
Done. Exceptions are documented and properly catched in cli.py code. |
| 42 |
---------------------------------------------------------------------- |
| 43 |
> Task: integration tests and documentation |
| 44 |
> Update documentation and write some integration tests. |
| 45 |
|
| 46 |
Partly done. Tests still need some love, but that will not be part of |
| 47 |
the GSOC (I still have to properly implement SrcUriNamer.) |
| 48 |
---------------------------------------------------------------------- |
| 49 |
|
| 50 |
GSoC is over, I have met my deliverables. It was a lot of fun, can't |
| 51 |
wait for Gentoo community to start using my tool. Project is far far |
| 52 |
from finished, I will continue to work on it and polish it. At the end, |
| 53 |
Gentoo is my primary choice for platform (even on laptop). |
| 54 |
|
| 55 |
I can't wait for next year to apply for the project and continue to work |
| 56 |
on OSS. Cheers guys! |
| 57 |
Thanks to my mentor Jesus for supporting me and thanks to Gentoo |
| 58 |
community for IRC 0day help! :) |
Archives