| 1 |
Hello, |
| 2 |
|
| 3 |
I am the student doing the Universal Select Tool for this year's |
| 4 |
Geetoo's SoC. |
| 5 |
|
| 6 |
On Tue, 2009-05-26 at 16:35 +0200, Philipp Riegger wrote: |
| 7 |
|
| 8 |
> |
| 9 |
> How will that tool be called? Maybe uselect? |
| 10 |
|
| 11 |
Everything points out to that until now. =) |
| 12 |
|
| 13 |
The way it's done, current eselect modules can continue working with |
| 14 |
uselect with very few changes needed. I didn't want to add full |
| 15 |
backwards compatibility because the utilities are slightly different and |
| 16 |
therefore creating the sense that uselect is not yet another eselect. At |
| 17 |
this time (SoC starts in a few hours) the prototype is written in |
| 18 |
python, does everything eselect does and supports any scripting language |
| 19 |
for module's actions. Oh, it's extremely faster too. Drop me a line at |
| 20 |
"[gentoo-dev] Google SoC @ Gentoo - Universal Select Tool" thread if you |
| 21 |
have any ideas. Thank you! |
| 22 |
|
| 23 |
Cheers, |
| 24 |
Sérgio |
Archives