| 1 |
On Sun, 2009-05-10 at 18:56 -0400, Mark Loeser wrote: |
| 2 |
> Sérgio Almeida <mephx.x@×××××.com> said: |
| 3 |
> > Abstract: |
| 4 |
> > |
| 5 |
> > Universal Select Tool is an utility to manage system configuration. |
| 6 |
> > This tool is similar to the unmaintained eselect utility of Gentoo or |
| 7 |
> > Exherbo's eclectic. The idea is to create a tool that manages both |
| 8 |
> > system settings and user settings with profile creation possibilities. |
| 9 |
> > The utility will use mostly concepts from "modules", "softenv", and |
| 10 |
> > both "eselect" and "eclectic". |
| 11 |
> |
| 12 |
> I guess this is a very high level question...but do we need yet another |
| 13 |
> eselect? Why can't we enhance or fix what we already have rather than |
| 14 |
> creating everything from scratch? |
| 15 |
> |
| 16 |
|
| 17 |
Mark, |
| 18 |
|
| 19 |
>From my point of view, uselect is not YA eselect. eselect wasn't thought |
| 20 |
from the beginning to be universal and therefore it would need a full |
| 21 |
re-write as you suggest. At this point (and SoC hasn't yet started) I |
| 22 |
have implemented uselect with all eselect capabilities in python (served |
| 23 |
as well to un-rust myself from python programming) and it is extremely |
| 24 |
faster. uselect supports modules in any scripting language (implemented |
| 25 |
too) and eselect only supports bash. uselect new architecture supports |
| 26 |
the auto-creation of simple symlinking/environment/alias modules (most |
| 27 |
of them will be it) using only a few regular expressions to define what |
| 28 |
to change and not how to change (uselect will do it for you). |
| 29 |
|
| 30 |
At this point eselect may be considered deprecated as it's |
| 31 |
functionalities are limited and there is no much we can do besides |
| 32 |
bloating bash code (what you call enhance) and bugfixing. |
| 33 |
|
| 34 |
Let us all consider uselect another utility with some "similar" |
| 35 |
functionalities from eselect but with a lot more features from modules |
| 36 |
and softenv. |
| 37 |
|
| 38 |
I knew your question would pop up and it is important to everyone to |
| 39 |
know the differences between the two utilities. |
| 40 |
|
| 41 |
I will post (in a near future) an example package for everyone to test |
| 42 |
and give it's opinion on how should every idea work instead of leaving |
| 43 |
all the decisions to me. |
| 44 |
|
| 45 |
Thanks. |
| 46 |
|
| 47 |
Cheers, |
| 48 |
Sérgio |
| 49 |
-- |
| 50 |
Sérgio Almeida <mephx.x@×××××.com> |
| 51 |
mephx @ freenode |
Archives