| 1 |
On 2022.07.05 12:24, Grant Edwards wrote: |
| 2 |
> On 2022-07-05, William Kenworthy <billk@×××××××××.au> wrote: |
| 3 |
> |
| 4 |
> > I synced portage a couple of days now and now my systems are |
| 5 |
> rebuilding |
| 6 |
> > python modules for 3.10 without any input from me [...] |
| 7 |
> |
| 8 |
> Every time there's a Python upgrade like this, it turns into a bit of |
| 9 |
> an ordeal because I always have a small handful of packages that don't |
| 10 |
> support the newer version. |
| 11 |
> |
| 12 |
> The news item offers no advice on what to do in this situation other |
| 13 |
> than completely postponing the upgrade of everything (which doesn't |
| 14 |
> seem like the best choice.) |
| 15 |
> |
| 16 |
> It would be nice if the news item explained how to let the upgrade |
| 17 |
> procede while holding back a few packages. |
| 18 |
> |
| 19 |
> Can you set 3_9 and 3_10 globally, and then disable 3_10 for a few |
| 20 |
> individual packages that can't be built with 3_10? |
| 21 |
As far as I can tell, you just need to add python_targets_python3_9 for |
| 22 |
the package in the appropriate package.use file. |
Archives