public inbox for gentoo-soc@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Domen Kožar" <domen@dev.si>
To: gentoo-soc <gentoo-soc@lists.gentoo.org>
Subject: [gentoo-soc] GSOC weekly report #7 and #8:  g-pypi
Date: Tue, 20 Jul 2010 16:59:53 +0200	[thread overview]
Message-ID: <1279637993.6228.12.camel@oblak> (raw)

[-- Attachment #1: Type: text/plain, Size: 2857 bytes --]

Blog post:
http://www.fubar.si/2010/7/20/gpypi2-google-summer-of-code-week-7-and-8

------------------------------------------------------
Plain text version:

Greetings, following is the weekly update for gpypi2 project. It's main
purpose is to generate ebuilds from Python Package Index. Quick links to
project info:

Repository, issue tracker: http://bitbucket.org/iElectric/g-pypi2
Hudson CI instance: http://hudson.fubar.si/job/g-pypi2/
Sphinx documentation generated by hudson on each commit:
http://docs.fubar.si/gpypi2/

Very successful 2 weeks. Two days of vacations and nice shiney
configuration utility together with questionnaire.

==============================================
Previous 2 weeks (5th - 19th July)
==============================================

----------------------------------------------------------------------------
Task: Write configuration skeleton
Currently, gpypi2 code only takes configuration from command line.
I'd like to extend that to config file (.ini), get data directly from
setup.py
and interactive questionaire. In order for that to function properly,
configuration needs to be done in right sequence.
Following week I will write down the design and implement initial
working prototype.
----------------------------------------------------------------------------

Configuration dispatcher fully implemented! Also we have already working
questionnaire functionality. Details can be found at
http://docs.fubar.si/gpypi2/userguide.html#configuration

----------------------------------------------------------------------------
Task: sync command - populate overlay with successful ebuilds from pypi
When I will get bored or stuck with task #1, I'll start working on
command that will
generate ebuilds from all packages in pypi to an overlay.
----------------------------------------------------------------------------

Initial "sync" command is implemented. Still lacking proper error
handling, metadata generation and manifest update support. Will be a lot
easier to implement with current configuration management.


Additional, following mini-tasks were performed:

* fixed echo command to work properly
* correct handling of whitespace in rendered ebuilds
* replace 4 spaces with a tab in rendered ebuilds

==========================================================
Upcoming week (20th - 26th July)
==========================================================


Task: fix TODOs in the code
Code currently has about 60 TODOs that need to be address for a better
codebase.

Task: Implement "python setup.py bdist_ebuild" command
I'll peek into distutils heart and implement most basic bdist command to
output an ebuild.
I will basically the same stuff we currently do,
except it will parse data from setup.py itself and not through pypi.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

                 reply	other threads:[~2010-07-20 15:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1279637993.6228.12.camel@oblak \
    --to=domen@dev.si \
    --cc=gentoo-soc@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox