| 1 |
>>>>> On Wed, 16 Apr 2008, Ciaran McCreesh wrote: |
| 2 |
|
| 3 |
> Blocks do not work: |
| 4 |
|
| 5 |
> * It's often not obvious what the user's supposed to do to resolve a |
| 6 |
> block. |
| 7 |
|
| 8 |
> * Once the user has worked out how to resolve the block correctly, |
| 9 |
> it's often hard to do so since resolving some blocks is best done by |
| 10 |
> forcibly ignoring the block, doing the install and then doing the |
| 11 |
> uninstall. |
| 12 |
|
| 13 |
> * It's often not obvious why a block is even there. |
| 14 |
|
| 15 |
> * They force the user to do a lot of work that isn't really |
| 16 |
> necessary. The package manager can be told how to resolve the block |
| 17 |
> in many cases, and the package manager can, with the user's |
| 18 |
> permission, do all the work is itself. |
| 19 |
|
| 20 |
I don't know if it would be feasible from a package manager point of |
| 21 |
view, but couldn't some (most?) blockers be avoided if there was some |
| 22 |
means to transfer ownership of installed files from one package to |
| 23 |
another? |
| 24 |
|
| 25 |
>> c) Marking that a file that used to be provided by one package is |
| 26 |
>> now provided by another package that is either depending upon or |
| 27 |
>> depended upon by the original package. |
| 28 |
|
| 29 |
>> d) Marking that a package has been moved into another package. |
| 30 |
|
| 31 |
At least these two common cases could then be avoided most of the |
| 32 |
time. |
| 33 |
|
| 34 |
Ulrich |
| 35 |
-- |
| 36 |
gentoo-dev@l.g.o mailing list |
Archives