| 1 |
On 2/4/2010 10:43 AM, Neil Bothwick wrote: |
| 2 |
> On Thu, 4 Feb 2010 16:14:25 +0200, Alan McKinnon wrote: |
| 3 |
> |
| 4 |
>>> How about giving the same warning when unmerging a dependency of |
| 5 |
>>> @system as you do when unmerging a package directly in there. Either |
| 6 |
>>> way, you risk breaking the system. |
| 7 |
>> |
| 8 |
>> Aren't all deps of packages in @system themselves already in @system? |
| 9 |
> |
| 10 |
> No, otherwise portage would complain if you tried to unmerge python. |
| 11 |
> Anyway, deps are USE-dependent. Try USE="X" emerge @system on a headless |
| 12 |
> server to see jut how much @system can pull in. |
| 13 |
|
| 14 |
Portage isn't in @system, either. "virtual/portage" is, but paludis |
| 15 |
also provides that. Python isn't a dependency of any other system |
| 16 |
package (except "file", but that's only enabled by the USE flag). |
| 17 |
|
| 18 |
It appears that portage's refusal to unmerge itself is hard-coded into |
| 19 |
portage; that reinforces my belief that portage should be responsible |
| 20 |
for refusing to unmerge it's own dependencies. |
| 21 |
|
| 22 |
--Mike |
Archives