1 |
28.2.2006, 21:39:43, Mike Frysinger wrote: |
2 |
|
3 |
> whats your point ? if an ebuild author wants to control the SLOT, then |
4 |
> they should be able to without having an invalid warning issued on the |
5 |
> subject |
6 |
|
7 |
> considering the nature of the warning, it should be trivial to make it into a |
8 |
> proper QA check by having the class see where files were installed and then |
9 |
> warn/abort if certain conditions are met |
10 |
|
11 |
> there's no reason for the user to see this crap |
12 |
> -mike |
13 |
|
14 |
Yeah, and there's no reason for user to see USE_EXPAND QA notice crap, |
15 |
eclass inherited illegally crap and a couple of others - this isn't going |
16 |
anywhere. |
17 |
|
18 |
You are trying to solve something that noone ever complained about. Why not |
19 |
rather solve stuff like ebuilds that depend unconditionally on arts, but |
20 |
because they inherit kde eclass they get bogus arts use flag from the |
21 |
eclass. This is an issue that's truly confusing and that people are filing |
22 |
bugs about. There's the difference between doing something useful and |
23 |
wasting time on an artificially invented issue. |
24 |
|
25 |
-- |
26 |
|
27 |
jakub |