1 |
Hello! |
2 |
|
3 |
|
4 |
When browsing through emerge logs (using elogv) I often come across |
5 |
stuff that doesn't affect me. Two examples: |
6 |
|
7 |
x11-base/xorg-server-1.7.6 warns: |
8 |
You must rebuild all drivers if upgrading from xorg-server 1.6 |
9 |
or earlier, because the ABI changed. |
10 |
|
11 |
dev-db/mysql-5.1.45-r1 logs: |
12 |
You might want to run: "emerge --config =dev-db/mysql-1.45-r1" |
13 |
if this is a new install. |
14 |
|
15 |
I had xorg 1.7.x running before so that's pure noise in my case. |
16 |
Same with mysql - I had it installed before. |
17 |
|
18 |
|
19 |
So I am wondering: Why aren't people using has_version to catch such |
20 |
cases and omit things that we have seen before or that don't affect us? |
21 |
|
22 |
has_version -- "Returns 1 if the system has the requested |
23 |
version of a certain package. For instance |
24 |
has_version >=sys-libs/glibc-2.3.0." |
25 |
|
26 |
|
27 |
Is it lazyness? Is it unawareness? Is there some kind of evilness in |
28 |
this usage of has_version that I am not aware of? |
29 |
Do we need a better framework for this? If so what could it look like? |
30 |
|
31 |
|
32 |
What do you think? |
33 |
|
34 |
|
35 |
|
36 |
Sebastian |