1 |
Hello all, |
2 |
|
3 |
long story short: |
4 |
|
5 |
when there is a major change (new gcc, new libc, and so on), tinderbox takes a |
6 |
lot of time to test the entire tree. |
7 |
|
8 |
Let's do a practical example: |
9 |
A new version of sys-devel/gcc is added to the tree. |
10 |
|
11 |
There is no way to know how much packages compiles C/C++ code, so the easiest |
12 |
way is compile the entire tree. |
13 |
|
14 |
Instead, imagine that each ebuild declares a variable called SOURCETYPE ( or |
15 |
similar, or in metadata.xml if you prefer ) and with a tool like equery/eix we |
16 |
are able to get the list of all packages that compiles C code. |
17 |
|
18 |
The same thing applies to other languages like python, ruby, go and so on |
19 |
where compile the dev-$language category covers a lot of packages, but there |
20 |
will be always other ebuilds that uses $language in other categories. |
21 |
|
22 |
What do you think? |
23 |
|
24 |
Agostino |