| 1 |
On 30/04/12 10:12, Ulrich Mueller wrote: |
| 2 |
>>>>>> On Mon, 30 Apr 2012, Michał Górny wrote: |
| 3 |
>> Since lately Gentoo devs force you to replace collision-protect with |
| 4 |
>> protect-owned [1] and sometimes packages just spit out files randomly |
| 5 |
>> on the filesystem due to random errors, I thought it may be a good idea |
| 6 |
>> to provide a new feature limiting the locations where packages can |
| 7 |
>> install. |
| 8 |
> |
| 9 |
> If the eclass doesn't work with FEATURES="collision-protect" then it |
| 10 |
> needs to be fixed. |
| 11 |
|
| 12 |
Long story short: older eclass compiled Python byte code in live file system, |
| 13 |
new one does it in src_install so .pyo/.pyc gets properly recorded, so the |
| 14 |
package *has to overwrite* files that are not owned by anyone (no package owns |
| 15 |
them). I've talked to Zac and: |
| 16 |
|
| 17 |
>>> |
| 18 |
There's not much else you can do. However, FEATURES="protect-owned" is |
| 19 |
enabled by default, and it will work fine if the .pyo and .pyc files are |
| 20 |
not owned by anything. I don't know why people use |
| 21 |
FEATURES="collision-protect", but at least you can tell them that |
| 22 |
they'll still have a reasonable level of protection from |
| 23 |
FEATURES="protect-owned" (it protect against file collisions between |
| 24 |
packages). |
| 25 |
<<< |
| 26 |
|
| 27 |
If you want to help feel free to suggest *how* to fix it, patches are especially |
| 28 |
welcomed :) |
| 29 |
|
| 30 |
-- |
| 31 |
Krzysztof Pawlik <nelchael at gentoo.org> key id: 0xF6A80E46 |
| 32 |
desktop-misc, java, vim, kernel, python, apache... |
Archives