1 |
Hello List ans anyone! |
2 |
|
3 |
I'm searching for a feature or an hint how and where to implement it. |
4 |
|
5 |
The desired feature could be called "stabilize" or "update to stable" |
6 |
and would change the selected packages when doing an update (emerge |
7 |
-avuND world). |
8 |
Just to give you an initial idea/example, some packages: |
9 |
package A - (the old_stable) has: 3.0 3.4 3.8 ~3.9 |
10 |
package B - (the young_stable) has: ~1.3 ~1.4 ~1.6 |
11 |
package C - (the unstable) has: ~0.6 ~0.8 ~1.1 |
12 |
So version numbers with the ~ are unstable/~amd64, where numbers without |
13 |
are stable/amd64. |
14 |
|
15 |
Case 1 (amd64): using system wide only stable/amd64 |
16 |
Installing anything would result in A@3.8 and C,B not installed |
17 |
|
18 |
Case 2 (~amd64): using system wide the unstable/~amd64 keyword |
19 |
Installing anything would result in A@~3.9 B@~1.6 C@~1.1 |
20 |
|
21 |
Case 3 ("real world"): get it managed with masks and keywords that the |
22 |
major packages are stable, while new features could arrive |
23 |
Installing anything with the result A@3.8 B@~1.6 C@~1.1 |
24 |
|
25 |
Nothing new so far, now new package versions arrive: |
26 |
package A - (the old_stable) has: 3.0 3.4 3.8 ~3.9 NEW: 4.0 ~4.1 |
27 |
package B - (the young_stable) has: ~1.3 ~1.4 ~1.6 NEW: 1.8 ~1.9 |
28 |
package C - (the unstable) has: ~0.6 ~0.8 ~1.1 NEW: ~1.2 ~1.4 |
29 |
|
30 |
So if we now update (emerge -avuND) right now the results are: |
31 |
Case 1 (amd64): Update A@3.8 to 4.0, B,C not installed |
32 |
Case 2 (~amd64): Update A@~3.9 to ~4.1, B@~1.6 to ~1.9, C@~1.1 to ~1.4 |
33 |
Case 3 ("real world"): depends on the new set of masks and keywords... |
34 |
much work ahead |
35 |
|
36 |
What I search is the stabilize feature for the update e.g. (emerge |
37 |
-avusND) should result in: |
38 |
Case 1 (amd64): |
39 |
- update A@3.8 to A@4.0, because a new stable version updates the old |
40 |
stable version |
41 |
- B, C not installed |
42 |
|
43 |
Case 2 (~amd64): |
44 |
- update A@~3.9 to A@4.0 update unstable packages to the stable |
45 |
version when arrived, stop using unstable. |
46 |
- update B@~1.6 to B@1.8 update unstable packages to the stable |
47 |
version when arrived, stop using unstable. |
48 |
- update C@~1.1 to C~1.4 update unstable packages, the never unstable |
49 |
versions. |
50 |
|
51 |
Case 3 ("real world"): |
52 |
- update A@3.8 to A@4.0 update stable package to newer stable version |
53 |
when arrived. |
54 |
- update B@~1.6 to B@1.8 update unstable packages to the stable |
55 |
version when arrived, stop using unstable. |
56 |
- update C@~1.1 to C~1.4 update unstable packages, the never unstable |
57 |
versions. |
58 |
Optional: make is possible to ignore/filter/select the unstable to |
59 |
unstable updates, those might cause trouble. |
60 |
|
61 |
|
62 |
Anyone, could help me? Give me a hint if this would be possible? Any |
63 |
hints where in code this could be implemented? I'm programmer, |
64 |
professional, so if I get the right hints, will invest spare time in |
65 |
this. Also I'll ready to setup and run various tests. But I never before |
66 |
worked at portage... |
67 |
It might be a good start if the people with the Know-How, will start a |
68 |
discussing about this idea, what problems need to be solved, which code |
69 |
parts will need an update and so one. Than I could try to get it |
70 |
working, but right now, I doesn't even know the right questions. |
71 |
|
72 |
Best regards, |
73 |
- Johannes Kellner |
74 |
|
75 |
-- |
76 |
------------------------------------------------------------------------------ |
77 |
Johannes Kellner |
78 |
freiberuflicher Informatiker |
79 |
|
80 |
Gostritzer Str. 12, 01217 Dresden, Germany |
81 |
Mobil: +49 162 4145161 |
82 |
Home: +49 351 4087058 |
83 |
contact@××××××××××××××××.eu |
84 |
www.johannes-kellner.eu |
85 |
UStId: DE 2568 79021 |
86 |
------------------------------------------------------------------------------ |