| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Ravi Pinjala wrote: |
| 5 |
> Even so, that still requires the user to know something about ebuild |
| 6 |
> writing, and maintain a personal overlay. People are much more likely to |
| 7 |
> already know how to install packages from source tarballs; it ought to |
| 8 |
> be possible to install a package (and have the PM be aware of it) using |
| 9 |
> just that knowledge. |
| 10 |
|
| 11 |
If the barrier to writing an ebuild appears to be to high then maybe |
| 12 |
we just need some better documentation to guide people through the |
| 13 |
process. It's really not difficult to write ebuilds. It will be more |
| 14 |
beneficial to encourage people to write ebuilds than to have them |
| 15 |
use some other approach that will require them to do essentially the |
| 16 |
same tasks as they would have to perform in order to write an ebuild |
| 17 |
(and have to repeat those tasks each time they install the package |
| 18 |
instead of encoding the steps in an ebuild). |
| 19 |
- -- |
| 20 |
Thanks, |
| 21 |
Zac |
| 22 |
-----BEGIN PGP SIGNATURE----- |
| 23 |
Version: GnuPG v2.0.10 (GNU/Linux) |
| 24 |
|
| 25 |
iEYEARECAAYFAknAIugACgkQ/ejvha5XGaMbWQCg7wYtPuO9G7cQlShGBdRzsUPH |
| 26 |
k24AnRKYRizTRzWoIzBH/QWS8fO3i6sT |
| 27 |
=rOGp |
| 28 |
-----END PGP SIGNATURE----- |
Archives