public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Issues with Python 3.8?
Date: Thu, 3 Jun 2021 11:29:06 +0100	[thread overview]
Message-ID: <20210603112906.464f85a3@phoucgh> (raw)
In-Reply-To: <CAJjrzcXfZz=RdOSCcYSJAnVaWzQky5=g8zGaTKe6DCbTNWKENw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1213 bytes --]

On Thu, 3 Jun 2021 10:48:25 +0200, Arve Barsnes wrote:

> > I've got several packages complaining about "PYTHON_TARGETS" missing
> > "python3_8":
> >
> >   The following REQUIRED_USE flag constraints are unsatisfied:
> >     python_targets_python3_8
> >
> >   The above constraints are a subset of the following complete
> > expression: any-of ( python_targets_python3_8 )
> >
> > I saw the news-item, but it doesn't specify what to do with packages
> > that only list 3.8 and occasionally 3.7.  
> 
> You can add 3.8 as a target on a specific package by specifying the
> USE flag 'python_targets_python3_8' for it.
> 
> If you decide to go that route, I recommend doing that only on a
> specific package version. You will then be required to keep up with
> the package if a new version is released that still does not have 3.9
> available, but you will automatically be rid of the 3.8 dependency on
> that package whenever a version is released that can be upgraded to
> 3.9.

I'd also put them in a separate file in /etc/portage/package.use, that
way you can review and remove the changes easily.


-- 
Neil Bothwick

ASSISTANT MANAGER: Feminine form of the word manager (q.v.).

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-06-03 10:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-03  8:19 [gentoo-user] Issues with Python 3.8? J. Roeleveld
2021-06-03  8:48 ` Arve Barsnes
2021-06-03 10:29   ` Neil Bothwick [this message]
2021-06-03  8:53 ` Adam Carter
2021-06-03  9:02   ` J. Roeleveld
2021-06-03  9:14     ` Adam Carter
2021-06-03 15:01 ` Jack

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210603112906.464f85a3@phoucgh \
    --to=neil@digimed.co.uk \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox