| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Arun Raghavan wrote: |
| 5 |
> 2009/3/18 Zac Medico <zmedico@g.o>: |
| 6 |
> [...] |
| 7 |
>> If the barrier to writing an ebuild appears to be to high then maybe |
| 8 |
>> we just need some better documentation to guide people through the |
| 9 |
>> process. It's really not difficult to write ebuilds. It will be more |
| 10 |
>> beneficial to encourage people to write ebuilds than to have them |
| 11 |
>> use some other approach that will require them to do essentially the |
| 12 |
>> same tasks as they would have to perform in order to write an ebuild |
| 13 |
>> (and have to repeat those tasks each time they install the package |
| 14 |
>> instead of encoding the steps in an ebuild). |
| 15 |
> |
| 16 |
> How about having a newbie version of skel.ebuild which has a small |
| 17 |
> comment for each field so people can just fill those in and get going? |
| 18 |
|
| 19 |
What's wrong with the existing skel.ebuild that we have already? It |
| 20 |
seems to me like a decent starting place for newbies, but they'll |
| 21 |
certainly need more that just that. What I had in mind is a concise |
| 22 |
tutorial that guides the reader through the basics of writing a |
| 23 |
really simple ebuild. It should be as concise as possible, in order |
| 24 |
to enable the reader to create and install their first simple ebuild |
| 25 |
without having to invest much time (sort of like a "hello world" |
| 26 |
tutorial for ebuilds). The tutorial should include a "resources" |
| 27 |
section which contains links to more comprehensive forms of |
| 28 |
documentation. |
| 29 |
- -- |
| 30 |
Thanks, |
| 31 |
Zac |
| 32 |
-----BEGIN PGP SIGNATURE----- |
| 33 |
Version: GnuPG v2.0.10 (GNU/Linux) |
| 34 |
|
| 35 |
iEYEARECAAYFAknAqZEACgkQ/ejvha5XGaNmOQCg4U8u9yJ1WCWVsCL87wCM18kg |
| 36 |
2NEAniiofHxhgeFzZe/v/PTUdMD24s9l |
| 37 |
=BC+Q |
| 38 |
-----END PGP SIGNATURE----- |
Archives