1 |
On Sat, Jul 16, 2022 at 06:46:40PM +0000, Robin H. Johnson wrote: |
2 |
> On Sat, Jul 16, 2022 at 09:31:35PM +0300, Arthur Zamarin wrote: |
3 |
> > I want to give another option. Both ways are allowed by eclass, but by |
4 |
> > QA policy (or some other decision), it is prohibited to use EGO_SUM in |
5 |
> > main ::gentoo tree. |
6 |
> > |
7 |
> > As a result, overlays and ::guru can use the EGO_SUM or dist distfile |
8 |
> > (remember, they don't have access to hosting on dev.g.o). |
9 |
> Yes; this is the option I was trying to propose as an intermediate step |
10 |
> until we have indirect Manifests that provide the best of both worlds |
11 |
> (not bloating the tree, and not requiring creation of dep tarballs). |
12 |
|
13 |
I could force this in the eclass with the following flow if I know how |
14 |
to tell if the ebuild inheriting it is in the main tree or not: |
15 |
|
16 |
# in_main_tree is a place holder for a test to see if the ebuld running |
17 |
# this is in the tree |
18 |
if [[ -n ${EGO_SUM} && in_main_tree ]]; then |
19 |
eqawarn "EGO_SUM is not allowed in the main tree" |
20 |
eqawarn "This will become a fatal error in the future" |
21 |
fi |
22 |
|
23 |
The only question is, is there a way to reliably tell whether or not |
24 |
we are in the main tree? |
25 |
|
26 |
William |