From: "Sérgio Almeida" <mephx.x@gmail.com>
To: Gentoo SoC <gentoo-soc@lists.gentoo.org>,
Gentoo Dev <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] Progress on Universal Select Tool
Date: Tue, 16 Jun 2009 15:48:35 +0100 [thread overview]
Message-ID: <1245163715.14589.515.camel@thedude> (raw)
[-- Attachment #1: Type: text/plain, Size: 1551 bytes --]
Hello,
Current State of Universal Select Tool - uselect
Proposal link:
http://socghop.appspot.com/student_project/show/google/gsoc2009/gentoo/t124022356237
uselect implementation started a few weeks before SoC officially started
to "de-rust" myself on python programming.
Here follows a checklist of what it already does right now.
* modules syntax defined
* modules support any scripting language
* module conversion from eselect to uselect are very easy (even when not
symlinking)
* per-user/system-wide actions
* simple symlinking actions are defined in 1 line only. uselect does all
the job.
* changing a user python interpreter through adding ~/.uselect/bin to
PATH through /etc/profile (is this the better way?)
Next steps:
* look deeper into eselect already implemented functions that most
modules use (by using inherit) and see what is uselect still lacking
* define profiling system (nice thread on gentoo-dev on this)
* start the profile system implementation
* start using gentoo's git
Further Notes:
* At this point I am ahead on schedule because of my early start. With
this I have plenty of time to implement features that were not described
on the proposal.
* Soon I will push the code into gentoo's git. If you have time, take a
look at it. Hope these reports are taken also as a "call for ideas".
Hope I'm not lacking any information. I'm loving working with Gentoo on
this. Learned a lot until now.
Cheers,
Sérgio
--
Sérgio Almeida - mephx.x@gmail.com
mephx @ freenode
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2009-06-16 14:49 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-16 14:48 Sérgio Almeida [this message]
2009-06-17 18:32 ` [gentoo-dev] Re: Progress on Universal Select Tool Sérgio Almeida
2009-06-29 18:50 ` Sérgio Almeida
2009-06-29 19:02 ` [gentoo-dev] Re: [gentoo-soc] " Sebastian Pipping
2009-06-29 19:42 ` Sérgio Almeida
2009-07-13 15:36 ` [gentoo-dev] " Sérgio Almeida
2009-07-14 9:20 ` Michael Haubenwallner
2009-07-15 15:42 ` Sérgio Almeida
[not found] ` <1247582117.3651.3.camel@thedude>
[not found] ` <1247584057.14345.29.camel@sapc154.salomon.at>
2009-07-15 15:43 ` Sérgio Almeida
2009-07-16 6:22 ` Michael Haubenwallner
2009-07-22 18:41 ` Sérgio Almeida
2009-07-23 3:09 ` [gentoo-dev] Re: [gentoo-soc] " Nirbheek Chauhan
2009-07-23 4:43 ` Sérgio Almeida
2009-07-23 5:32 ` Nirbheek Chauhan
2009-07-23 13:35 ` Sérgio Almeida
2009-07-23 15:28 ` Robert Buchholz
2009-07-23 18:33 ` Sérgio Almeida
2009-07-24 8:22 ` Michael Haubenwallner
2009-07-24 15:20 ` Sérgio Almeida
2009-07-27 8:33 ` Michael Haubenwallner
2009-07-27 18:35 ` Sérgio Almeida
[not found] ` <6f8b45100907230047k44111c77ha1b68e61b8c88bf2@mail.gmail.com>
2009-07-23 13:40 ` Sérgio Almeida
2009-07-23 6:12 ` [gentoo-dev] " Duncan
2009-08-01 18:46 ` Sérgio Almeida
2009-08-18 15:23 ` Sérgio Almeida
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=1245163715.14589.515.camel@thedude \
--to=mephx.x@gmail.com \
--cc=gentoo-dev@lists.gentoo.org \
--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