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