| 1 |
I think the best way is to study the steps progressively. |
| 2 |
|
| 3 |
Once you've read the portage documentation ( and man files ) |
| 4 |
then start looking for simple packages that you could study each step off of.. |
| 5 |
|
| 6 |
net-misc/vnc was a good package for me to start with. |
| 7 |
app-editors/jed is a little more advanced. |
| 8 |
net-www/prozilla was also helpful |
| 9 |
x11-libs/qt shows some neat sed tricks to overcome interactivity |
| 10 |
app-editors/vim shows good use of 'USE' variable techniques. |
| 11 |
|
| 12 |
Another alternative is to look at bugs.gentoo.org and find a broken ebuild bug and try to fix |
| 13 |
that, thereby gaining experience through trial, error, and lots of questions. |
| 14 |
|
| 15 |
|
| 16 |
--- Pichai Asokan <pasokan@×××.com> wrote: |
| 17 |
> On Wed, Apr 17, 2002 at 01:50:31AM -0400, Sandy McArthur wrote: |
| 18 |
> > Pichai Asokan wrote: |
| 19 |
> > >Can some of the developers take a few minutes to suggest |
| 20 |
> > >the ebuilds to study for 'would be contributors'? |
| 21 |
> > |
| 22 |
> > Without being specific I'd say look at ones for software you have |
| 23 |
> > compiled on your own from the source in the past, that way you'll be |
| 24 |
> > familar with what should be going on. |
| 25 |
> Thanks; |
| 26 |
> but often it was a case of |
| 27 |
> (un)tar |
| 28 |
> ./configure |
| 29 |
> make |
| 30 |
> make install |
| 31 |
> Well; I could have looked at what went where, but I never did :-( |
| 32 |
> So I am not sure how much this will help. |
| 33 |
> P Asokan |
| 34 |
> _______________________________________________ |
| 35 |
> gentoo-dev mailing list |
| 36 |
> gentoo-dev@g.o |
| 37 |
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev |
| 38 |
|
| 39 |
|
| 40 |
__________________________________________________ |
| 41 |
Do You Yahoo!? |
| 42 |
Yahoo! Tax Center - online filing with TurboTax |
| 43 |
http://taxes.yahoo.com/ |
Archives