| 1 |
On 2022-07-05, Jack <ostroffjh@×××××××××××××××××.net> wrote: |
| 2 |
> On 2022.07.05 12:24, Grant Edwards wrote: |
| 3 |
>> On 2022-07-05, William Kenworthy <billk@×××××××××.au> wrote: |
| 4 |
|
| 5 |
>> It would be nice if the news item explained how to let the upgrade |
| 6 |
>> procede while holding back a few packages. |
| 7 |
>> |
| 8 |
>> Can you set 3_9 and 3_10 globally, and then disable 3_10 for a few |
| 9 |
>> individual packages that can't be built with 3_10? |
| 10 |
|
| 11 |
> As far as I can tell, you just need to add python_targets_python3_9 for |
| 12 |
> the package in the appropriate package.use file. |
| 13 |
|
| 14 |
I've tried that, and it takes forever. Everything time you do it, the |
| 15 |
next emerge attempt will fail because one of that package's |
| 16 |
dependencies doesn't have 3_9 set. So you set that one, do an emerge, |
| 17 |
and it fails because there's another depenency that doesn't have 3_9 |
| 18 |
set. Repeat this for an hour or two... |
| 19 |
|
| 20 |
If it would tell you about all of them at once, it wouldn't be so bad. |
| 21 |
But, if you're trying to hold back a large application with dozens and |
| 22 |
dozens of dependancies it makes you want to scream. |
| 23 |
|
| 24 |
Or doesn't it torture you like that any longer? |
| 25 |
|
| 26 |
-- |
| 27 |
Grant |
Archives