1 |
On 09/20/2010 07:30 PM, Alec Warner wrote: |
2 |
> Under the new system I can put the code: |
3 |
> |
4 |
> 1) In a global eclass, any ebuild can likely use it |
5 |
> 2) In a per-package eclass, only one package can use it |
6 |
> 3) In a pkg eblit, only one package can use it |
7 |
|
8 |
Per package eclasses are pretty much eblits with some PM support thrown in. |
9 |
|
10 |
> Wouldn't taking code from a global eclass and moving it to a |
11 |
> per-package eclass limit code re-use? |
12 |
|
13 |
No, code reuse will stay the same. What I like about the idea is moving |
14 |
more of the code closer to the ebuild files, tightening it's scope. No |
15 |
more wondering (as an ebuild author) if and how I could use |
16 |
php5_2-sapi.eclass - it just wouldn't be there. |
17 |
|
18 |
I'll answer more points tomorrow, but thanks for your ideas! |