| 1 |
On Tuesday 21 March 2006 12:32, Alec Warner wrote: |
| 2 |
> m h wrote: |
| 3 |
> > I'm not a gentoo dev (just a satisfied user), but I lurk on this list. |
| 4 |
> > |
| 5 |
> > I was at PyCon last month. I would estimate that about 40% of the |
| 6 |
> > people there ran linux on their laptops. The most popular distros |
| 7 |
> > were gentoo and ubuntu. (Not this is not a scientific study, just my |
| 8 |
> > observations from talking to people there). While I was there the |
| 9 |
> > person next to me starting hacking the ebuild classes to handles eggs |
| 10 |
> > (so he could emerge turbogears). I talked to at least 3 others who |
| 11 |
> > were running gentoo. I asked all of them if they had worked on |
| 12 |
> > portage. Most said "No, the code is a little scary". (I'll concur |
| 13 |
> > with that sentiment, as the code doesn't feel very pythonic). |
| 14 |
> > |
| 15 |
> > If you want to attract more developers (python people), a few things are needed: |
| 16 |
> |
| 17 |
> That depends on how they contribute, I personally don't want random |
| 18 |
> python master bob contributing pieces to portage itself. Portage things |
| 19 |
> are not necessarily as simple as people make them out to be. Even |
| 20 |
> developers who know the code well make mistakes in adding and removing |
| 21 |
> code. As solar once pointed out "the only man I trust to touch the |
| 22 |
> resolver is Jstubbs." I realize thats a bit elitest...but at the same |
| 23 |
> time...I am overly cautious ;) |
| 24 |
|
| 25 |
The resolver as it stands now is not overly difficult. One does really need |
| 26 |
to know it back to front though. I should really make splitting it out and |
| 27 |
documenting it my big project for 2.2. |
| 28 |
|
| 29 |
-- |
| 30 |
Jason Stubbs |
| 31 |
-- |
| 32 |
gentoo-dev@g.o mailing list |
Archives