| 1 |
On Wednesday 26 November 2003 13:01, Jason Mobarak wrote: |
| 2 |
> My only suggestion is to make your own code feature enough abstract |
| 3 |
> encapsulation of portage that you can easily change how it may interact |
| 4 |
> with future versions (i.e., MVC or similar design patterns). Currently I'm |
| 5 |
> working on separating portage into a library of python packages but it's |
| 6 |
> slow work and I currently have no one who seems greatly interested in |
| 7 |
> helping. Hopefully I'll be able to finish before the end of December. |
| 8 |
> |
| 9 |
> However, I am looking to add several things to the current portage, |
| 10 |
> documentation, unit tests, modularity, and encapsulation of basic |
| 11 |
> operations (possibly using interfaces to define what methods certain class |
| 12 |
> should have in order to perform certain actions). |
| 13 |
|
| 14 |
I'd be interested in helping in that. I don't have too much free time, have |
| 15 |
only just started using Python and have yet to understand how the more |
| 16 |
important functionality works (the digraph class and all the dep_ functions) |
| 17 |
but I'm a very quick learner and would only be a liability for a very short |
| 18 |
time. :-) |
| 19 |
|
| 20 |
Let me know if you're interested. |
| 21 |
|
| 22 |
Regards, |
| 23 |
Jason (too) |
| 24 |
|
| 25 |
-- |
| 26 |
gentoo-dev@g.o mailing list |
Archives