1 |
Ühel kenal päeval, K, 16.02.2022 kell 19:39, kirjutas Ulrich Müller: |
2 |
> Function vala_src_prepare did not call eapply_user, so it could not |
3 |
> be |
4 |
> used as a stand-alone phase function but must be called explicitly. |
5 |
> Rename it to vala_setup, which can be called either from pkg_setup or |
6 |
> from src_prepare. |
7 |
|
8 |
Just to clarify the reasons to drop the EXPORT - it's really about the |
9 |
fact that you can actually never use it automatically. Absolutely all |
10 |
packages that use vala.eclass need to define their own src_prepare in |
11 |
the ebuild anyways, in order to also call gnome_src_prepare, |
12 |
cmake_src_prepare, or xdg_src_prepare. |
13 |
So the exported phase had no value, as an ebuild author always needs to |
14 |
declare their own, so it's just confusing with the vala_src_prepare |
15 |
function naming from before. |
16 |
|
17 |
There may be some value in trying to do these steps in an exported |
18 |
pkg_setup instead, similar to the python eclasses (and what vala.eclass |
19 |
does is very similar to what the python eclasses do). But I fear it |
20 |
would just clash with python_pkg_setup then instead in many cases, as |
21 |
we get a lot of python-any-r1.eclass inheriting lately in meson + vala |
22 |
packages due to the python-exec[-native-symlinks] tinderbox runs. |
23 |
Though things are slowly moving away from needing this (meson added a |
24 |
gnome postinstall step that takes care of it natively, instead of |
25 |
needing custom python postinst scripts), so it'll probably get rarer to |
26 |
need python-any-r1 + vala together and a vala_pkg_setup might be of |
27 |
good value. |
28 |
Anyhow, enough of my rambling here. If someone would like to explore |
29 |
this option, great. If not, I think we should just get it to EAPI-8 |
30 |
with these changes and revisit with EAPI-9. |
31 |
|
32 |
|
33 |
Mart |