1 |
On Wed, 2018-02-14 at 23:43 +0100, Jonas Stein wrote: |
2 |
> Did I miss something? |
3 |
> Who can help to check with (an automatic) testenvironment, if these |
4 |
> packages will survive? |
5 |
|
6 |
Don't check with test environments, read the ebuilds. Test environments |
7 |
will find it hard to catch changes in the installed files. For example |
8 |
the first issue in that list I found was relying on the inherit for a |
9 |
make_desktop_entry call. In a test environment, it'll just not install |
10 |
a desktop entry while outputting a function not found call or something |
11 |
I suspect. You are lucky if that message is somehow parsed out, and |
12 |
then there are other similar issues possible. (In this example, |
13 |
inheriting desktop.eclass should be added to the ebuild before eclass |
14 |
drops the eutils inherit) |
15 |
|
16 |
If you want to do it, really should just read over all these ebuilds |
17 |
manually. A test environment has a hard time to catch some sort of |
18 |
conditional calls to eutils functions as well, when they don't enter |
19 |
that conditional block for any reason. |
20 |
I suspect most others than this xmind are rather simple ones that don't |
21 |
even have anything beyond declaring the DEPEND and other variables. |
22 |
|
23 |
Also start with the patch to bail out on unknown EAPI's that you were |
24 |
planning to do. This can be separate commit done before this change, |
25 |
once checks are done. Of course ideally pushed together (if the eutils |
26 |
drop pans out) to minimize cache regenerations for developers. |
27 |
|
28 |
|
29 |
Mart |