| 1 |
On Sun, 02 Oct 2005 19:58:19 -0400 Dave Nebinger <dnebinger@××××.com> |
| 2 |
wrote: |
| 3 |
| a) are there limits to the size and/or complexity of the ebuilds that |
| 4 |
| are accepted into portage? |
| 5 |
|
| 6 |
Well... |
| 7 |
|
| 8 |
* Whoever ends up maintaining said ebuild must understand it. |
| 9 |
* Too much complexity is often a sign that you're doing something |
| 10 |
wrong. |
| 11 |
* Too much complexity often suggests that an eclass is needed. |
| 12 |
* Too much complexity often suggests that upstream's build system is |
| 13 |
annoyingly broken. |
| 14 |
|
| 15 |
| b) If there are and I end up going beyond them, is there a |
| 16 |
| recommended methodology for relocating some of the functionality? I |
| 17 |
| mean, can I put code into scripts in the files directory and freely |
| 18 |
| execute from there? |
| 19 |
|
| 20 |
eclass. |
| 21 |
|
| 22 |
-- |
| 23 |
Ciaran McCreesh : Gentoo Developer (Vim, Shell tools, Fluxbox, Cron) |
| 24 |
Mail : ciaranm at gentoo.org |
| 25 |
Web : http://dev.gentoo.org/~ciaranm |
Archives