| 1 |
That is enough once you know how to write ebuilds. |
| 2 |
|
| 3 |
We were thinking of a GUI to soften the learning curve to non-experts. |
| 4 |
Probably not useful for a Gentoo developer, but could provide an easy way to |
| 5 |
write ebuilds to project maintainers themselves, not to Gentoo resources. |
| 6 |
|
| 7 |
On Thursday 08 February 2007 10:43, Ciaran McCreesh wrote: |
| 8 |
> On Thu, 8 Feb 2007 10:38:08 +0100 Jose San Leandro |
| 9 |
> |
| 10 |
> <jose.sanleandro@×××××××××.es> wrote: |
| 11 |
> | A friend of mine and myself are willing to develop some tools to help |
| 12 |
> | ebuild development. |
| 13 |
> |
| 14 |
> All the common cases should be handled by default functions, package |
| 15 |
> manager functions and eclasses. Thus, writing ebuilds should consist |
| 16 |
> merely of handling unique or uncommon special cases, and the best tool |
| 17 |
> for doing that is an ebuild-aware text editor. |
| 18 |
-- |
| 19 |
gentoo-dev@g.o mailing list |
Archives