-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Arun Raghavan wrote:
> 2009/3/18 Zac Medico <zmedico@g.o>:
> [...]
>> If the barrier to writing an ebuild appears to be to high then maybe
>> we just need some better documentation to guide people through the
>> process. It's really not difficult to write ebuilds. It will be more
>> beneficial to encourage people to write ebuilds than to have them
>> use some other approach that will require them to do essentially the
>> same tasks as they would have to perform in order to write an ebuild
>> (and have to repeat those tasks each time they install the package
>> instead of encoding the steps in an ebuild).
> 
> How about having a newbie version of skel.ebuild which has a small
> comment for each field so people can just fill those in and get going?

What's wrong with the existing skel.ebuild that we have already? It
seems to me like a decent starting place for newbies, but they'll
certainly need more that just that. What I had in mind is a concise
tutorial that guides the reader through the basics of writing a
really simple ebuild. It should be as concise as possible, in order
to enable the reader to create and install their first simple ebuild
without having to invest much time (sort of like a "hello world"
tutorial for ebuilds). The tutorial should include a "resources"
section which contains links to more comprehensive forms of
documentation.
- --
Thanks,
Zac
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.10 (GNU/Linux)

iEYEARECAAYFAknAqZEACgkQ/ejvha5XGaNmOQCg4U8u9yJ1WCWVsCL87wCM18kg
2NEAniiofHxhgeFzZe/v/PTUdMD24s9l
=BC+Q
-----END PGP SIGNATURE-----