public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: PYTHON_SINGLE_TARGET & libreoffice
Date: Sat, 27 Feb 2016 22:21:54 +0200	[thread overview]
Message-ID: <56D20562.1040108@gmail.com> (raw)
In-Reply-To: <nat067$vt9$1@ger.gmane.org>

On 27/02/2016 22:16, Nikos Chantziaras wrote:
> On 27/02/16 21:40, Alan McKinnon wrote:
>> I don't know much about PYTHON_SINGLE_TARGET and PYTHON_TARGET, it all
>> seemed to just work so I never looked further. Until now. Of all
>> packages, libreoffice seems to want only python3:
>>
>> I can set it in make.conf but as expected that causes all manner of
>> other packages to fail emerge checks as they need python2.7.
>>
>> What's the preferred way to deal with this situation?
> 
>   PYTHON_TARGETS="python2_7 python3_4"
>   PYTHON_SINGLE_TARGET="python3_4"
> 
> For packages that require another PYTHON_SINGLE_TARGET version, you can
> set "python_single_target_python2_7" in package.use. For example:
> 
>   app-text/asciidoc python_single_target_python2_7
> 
> The reverse is also true. You can set:
> 
>   PYTHON_SINGLE_TARGET="python2_7"
> 
> in make.conf, and then set "python_single_target_python3_4" in
> package.use for packages that require 3.4:
> 
>   app-office/libreoffice python_single_target_python3_4
> 
> I use the first method.
> 
> Yes, it's a PITA :-)

I'll say.

Just got another one - sigil. That fails at build time, not at
emerge-initial-check-stuff time. So no problem I thought, I'll tweak
that one too. Now that causes 20 packages in dev-python like eg pillow,
six, etc to want the same tweak. And boost.

I have free time, I'll experiment with those now. I just hope it doesn't
break everything else using those packages



> PS:
> Another syntax is also available for package.use:
> 
>   app-text/asciidoc <other USE flags> PYTHON_SINGLE_TARGET: python2_7
> 
> Just saw a blog post about it; I think it's undocumented and works for
> all USE_EXPAND flags. The downside is that it has to appear at the end
> of the line.
> 
> 


-- 
Alan McKinnon
alan.mckinnon@gmail.com



  reply	other threads:[~2016-02-27 20:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-27 19:40 [gentoo-user] PYTHON_SINGLE_TARGET & libreoffice Alan McKinnon
2016-02-27 19:59 ` Alec Ten Harmsel
2016-02-27 20:04   ` Alan McKinnon
2016-02-27 20:22     ` [gentoo-user] " Nikos Chantziaras
2016-02-27 20:36       ` Alan McKinnon
2016-02-27 20:16 ` Nikos Chantziaras
2016-02-27 20:21   ` Alan McKinnon [this message]
2016-02-27 20:27 ` »Q«
2016-02-27 20:37   ` Alan McKinnon
2016-02-27 20:49 ` [gentoo-user] " Todd Goodman
2016-02-27 21:22 ` Neil Bothwick

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=56D20562.1040108@gmail.com \
    --to=alan.mckinnon@gmail.com \
    --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