| 1 |
Hello, |
| 2 |
|
| 3 |
Regardless that firm pencil's down date has come for this year's GSoC as |
| 4 |
discussed with my mentor I will continue coding. These final weeks will |
| 5 |
be split between coding, documentation, sample module creation and |
| 6 |
polishing. Also a live ebuild creation is in progress. |
| 7 |
|
| 8 |
Comparing uselect with eselect: |
| 9 |
|
| 10 |
* uselect is much faster (even with lots of modules) |
| 11 |
* uselect can already use (in a very ugly way) all eselect's modules |
| 12 |
with a copy/paste step. It's still faster in this way. |
| 13 |
* uselect menu is much more user friendly even though it's based on |
| 14 |
eselect/ecletic. |
| 15 |
* uselect has a general user-profile schema (using a ~/.uselect/ |
| 16 |
folder). |
| 17 |
* uselect does not have a base function libraries as eselect does. |
| 18 |
uselect objective was to create a simple framework that needs no logic |
| 19 |
coding within modules. |
| 20 |
* uselect can be easily expanded with more action classes with not much |
| 21 |
coding as we are using an object based language with great inheritance |
| 22 |
features. |
| 23 |
|
| 24 |
Uselect is far from ready, but it's current state (besides usable) is |
| 25 |
"presentable". What do I mean by presentable? |
| 26 |
|
| 27 |
Uselect and Uprofile are a Proof of Concept of what both can be. I was |
| 28 |
expecting better interaction and belief in the Universal Select Tool |
| 29 |
project during all SoC. As most ideas/suggestions were purely based on |
| 30 |
necessity and not on community-wide contribution as suggestion for new |
| 31 |
action types templates a very solid and flexible framework was not |
| 32 |
achieved. A solid example (symlinking modules) is fully supported either |
| 33 |
user-wide and system-wide. A fine structure for .uselect folders |
| 34 |
and .uprofile folders was not strictly defined as it is a very |
| 35 |
decisional matter for general gentoo usability. Automatic module |
| 36 |
creation during emerge is not possible without major changes to ebuilds |
| 37 |
due to the lack of a list of "to-be-installed" files (there are ugly |
| 38 |
workarounds, but none are worth implementing). Module's API is very |
| 39 |
simple and can be easily changed from plain python to json or a similar |
| 40 |
markup language. Uprofile (as current concept was not in my initial |
| 41 |
proposal) is strictly a proof of concept of the interaction beween |
| 42 |
uprofile and uselect's API. Once documentation and examples are done |
| 43 |
uselect and uprofile will be ready to be presented to the gentoo |
| 44 |
community and to be discussed within gentoo's decision organs. |
| 45 |
|
| 46 |
It's been great to be working with gentoo. I hope that this tool gets |
| 47 |
integrated in gentoo and I am willing to continue developing it after |
| 48 |
SoC's end. |
| 49 |
|
| 50 |
Thanks to everyone that helped, especially my mentor bicatali, people at |
| 51 |
gentoo-dev@ and gentoo-soc@ and a few unknown folks at #python that |
| 52 |
helped me solve complex python class mutation problems and recursiveness |
| 53 |
paradoxes (this was the real deal). |
| 54 |
|
| 55 |
Will also continue posting weekly reports on gentoo-soc@ until soc ends. |
| 56 |
|
| 57 |
Cheers, |
| 58 |
Sérgio |
| 59 |
-- |
| 60 |
Sérgio Almeida - mephx.x@×××××.com |
| 61 |
mephx @ freenode |
Archives