| 1 |
On 03/19/2010 01:52 AM, Dale wrote: |
| 2 |
> I think what most people want is for portage not to pull in a package |
| 3 |
> that nothing uses. I'm not a dev nor a programmer but I have yet to see |
| 4 |
> any good reason for installing something that is not being used. It's |
| 5 |
> not being tested to see if it is stable. It would have to be used |
| 6 |
> before that would happen. Basically, it is just one more package to |
| 7 |
> update and taking up hard drive space. It's not doing anything else. |
| 8 |
|
| 9 |
It won't be pulled in unless something else is pulled in that "can |
| 10 |
use python3". |
| 11 |
|
| 12 |
> As for slots, if something needs it, portage would pull in the new |
| 13 |
> slot. That's what portage does. It just seems in this case it is |
| 14 |
> pulling in a new slot that nothing uses. |
| 15 |
|
| 16 |
The problem is, most people will have have something pulled in via |
| 17 |
dependencies that "can use python3", even though python-2.x will |
| 18 |
suffice. For cases like this, some users may want to use |
| 19 |
package.mask in order to prevent python3 from being installed. |
| 20 |
-- |
| 21 |
Thanks, |
| 22 |
Zac |
Archives