| 1 |
On Thu, Jan 05, 2006 at 11:42:36PM -0500, Andrew Muraco wrote: |
| 2 |
> Anyways, I would personally like to see if this can stir some interest. |
| 3 |
> I would be willing to help test and help make this GLEP a reality, |
| 4 |
> however I can not implement this myself as I lack python skills, but I |
| 5 |
> do want to help the portage team, as much as I can, to make this happen, |
| 6 |
> as I have some great benefit from this added feature. |
| 7 |
|
| 8 |
Whoever spear heads this is going to have to know at least a bit |
| 9 |
python, so I'd suggest you learn- pretty straightforward. Would |
| 10 |
suggest diveintopython.org for starters. |
| 11 |
|
| 12 |
Portage however, is not, but if you have questions you are welcome to |
| 13 |
ask in #-portage. Not saying we're going to do all of the legwork, |
| 14 |
but we are available as a resource. |
| 15 |
|
| 16 |
|
| 17 |
> Also, I hope I covered everything, and if the response from the mailing |
| 18 |
> list is good I may consider revising the existing GLEP and prepare it |
| 19 |
> for submittal to the council in feburary, or march, depending on how |
| 20 |
> much revision the GLEP needs, and if my idea is better or worse then the |
| 21 |
> current solution proposed. |
| 22 |
|
| 23 |
Probably better to iron out what y'all actually need and what the dev |
| 24 |
community is willing to put up with. |
| 25 |
|
| 26 |
Eg, would do some research into it, read the archives from last few |
| 27 |
wars over it, in general find (and address) the issues that lead to |
| 28 |
glep19 going still born. |
| 29 |
|
| 30 |
~harring |
Archives