1 |
Hi folks, |
2 |
|
3 |
|
4 |
just an idea spinning around in my head: |
5 |
|
6 |
Is it possible to influence the dependency resolution (eg. on virtuals) ? |
7 |
|
8 |
For example, several weeks ago somebody here asked on how to switch |
9 |
from jpeg to jpeg-turbo. For such cases it IMHO would be fine if |
10 |
there was some eselect which controls the behaviour of the |
11 |
virtual/jpeg package. Once he switched over via eselect, it would |
12 |
trigger the other jpeg implementation and (if necessary) rebuild |
13 |
of all depending packages on next emerge world. |
14 |
|
15 |
Could the current eselect + portage system provide this ? |
16 |
|
17 |
The whole idea could also be extended to packages which frequently |
18 |
require revdep-rebuild (eg. poppler): those packages would be |
19 |
slotted for parallel installation and an new virtual is introduced |
20 |
where clients will depend on (instead of the actual package directly) |
21 |
When new versions come out, the user will be tolld (eg. via eselect |
22 |
news) that he can now switch his system. Once he does the switch, |
23 |
new builds will be made against the new version and remaining |
24 |
packages (still linking to the old library) will be triggered |
25 |
for update. |
26 |
|
27 |
|
28 |
cu |
29 |
-- |
30 |
---------------------------------------------------------------------- |
31 |
Enrico Weigelt, metux IT service -- http://www.metux.de/ |
32 |
|
33 |
phone: +49 36207 519931 email: weigelt@×××××.de |
34 |
mobile: +49 151 27565287 icq: 210169427 skype: nekrad666 |
35 |
---------------------------------------------------------------------- |
36 |
Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme |
37 |
---------------------------------------------------------------------- |