1 |
On 06:24 Wed 16 Apr , Ciaran McCreesh wrote: |
2 |
> What all are blocks used for? |
3 |
> |
4 |
> a) Marking that two unrelated packages are mutually incompatible at |
5 |
> runtime because they happen to collide, for example on a commonly named |
6 |
> executable. |
7 |
> |
8 |
> b) Marking that two related implementations are mutually incompatible at |
9 |
> runtime because they both provide the same binary. |
10 |
> |
11 |
> c) Marking that a file that used to be provided by one package is now |
12 |
> provided by another package that is either depending upon or depended |
13 |
> upon by the original package. |
14 |
> |
15 |
> d) Marking that a package has been moved into another package. |
16 |
> |
17 |
> Are there any other uses? |
18 |
|
19 |
A slight tweak that you may have already considered: a single package is |
20 |
split into multiple packages with a metabuild (named the same as the |
21 |
original single package) in a newer version -- for example, modularized |
22 |
X. |
23 |
|
24 |
> For future EAPIs, being able to tell the package manager that your |
25 |
> block is of one of the types above will help the package manager smooth |
26 |
> out the upgrade path for users. For example, for class d) blocks such |
27 |
> as the recent coreutils / mktemp mess, the package manager can suggest |
28 |
> to the user to install the new package and then uninstall the old |
29 |
> package, rather than forcing the user to uninstall the old package by |
30 |
> hand (possibly leaving their system without critical utilities) and then |
31 |
> install the new package. |
32 |
> |
33 |
> I strongly suspect that in many (but not all) cases the package manager |
34 |
> could be making users' lives a lot easier than it currently is... |
35 |
|
36 |
Sounds like a great idea. |
37 |
|
38 |
Thanks, |
39 |
Donnie |
40 |
-- |
41 |
gentoo-dev@l.g.o mailing list |