[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gentoo-dev
Subject:    Re: [gentoo-dev] [PATCHES] python-r1.eclass: any-of dep API support
From:       Alex Turbov <i.zaufi () gmail ! com>
Date:       2017-05-21 2:44:34
Message-ID: CANktQttYkkcbJPGYe=+VXYvL9idkX2yhzgDXLv0xq_KK2P8inA () mail ! gmail ! com
[Download RAW message or body]

When it'll be possible to start to use it?

On Sat, May 20, 2017 at 8:30 PM, Micha=C5=82 G=C3=B3rny <mgorny@gentoo.org>=
 wrote:

> Hi, everyone.
>
> Here's a set of patches inspired by the recent Sphinx dependency
> discussion. They make python-r1 (and therefore distutils-r1) capable
> of any-of dependency logic similar to the one used in python-any-r1.
>
> The basic goal is relatively simple -- to improve handling of pure
> build-time dependencies in the eclass. It solves two common problems:
>
> a. dependencies on packages that support only a subset of PYTHON_COMPAT,
>
> b. dependencies that need to be implementation-bound between themselves
>    (e.g. Sphinx plugins).
>
> The new API improves both of those cases significantly. For the former,
> we no longer force user to select additional targets via REQUIRED_USE --
> instead, we just any-of dependencies + python_check_deps() to select
> implementation independently of whether it is enabled or not.
>
> For the latter, we no longer have to force all targets of the package
> on all the involved dependencies. Again, using any-of dep
> and appropriate python_check_deps() we can enforce a single (any)
> target throughout all the packages and use it.
>
> The first three patches do some code refactoring that makes the change
> easier and possibly improves maintainability of the code. The next two
> patches add support for python_check_deps() and python_gen_any_dep()
> respectively. The last two patches provide examples for both use cases
> mentioned.
>
> Please review.
>
> --
> Best regards,
> Micha=C5=82 G=C3=B3rny
>
>
>

[Attachment #3 (text/html)]

<div dir="ltr">When it&#39;ll be possible to start to use it?<br></div><div class="gmail_extra"><br><div \
class="gmail_quote">On Sat, May 20, 2017 at 8:30 PM, Michał Górny <span dir="ltr">&lt;<a \
href="mailto:mgorny@gentoo.org" target="_blank">mgorny@gentoo.org</a>&gt;</span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi, \
everyone.<br> <br>
Here&#39;s a set of patches inspired by the recent Sphinx dependency<br>
discussion. They make python-r1 (and therefore distutils-r1) capable<br>
of any-of dependency logic similar to the one used in python-any-r1.<br>
<br>
The basic goal is relatively simple -- to improve handling of pure<br>
build-time dependencies in the eclass. It solves two common problems:<br>
<br>
a. dependencies on packages that support only a subset of PYTHON_COMPAT,<br>
<br>
b. dependencies that need to be implementation-bound between themselves<br>
     (e.g. Sphinx plugins).<br>
<br>
The new API improves both of those cases significantly. For the former,<br>
we no longer force user to select additional targets via REQUIRED_USE --<br>
instead, we just any-of dependencies + python_check_deps() to select<br>
implementation independently of whether it is enabled or not.<br>
<br>
For the latter, we no longer have to force all targets of the package<br>
on all the involved dependencies. Again, using any-of dep<br>
and appropriate python_check_deps() we can enforce a single (any)<br>
target throughout all the packages and use it.<br>
<br>
The first three patches do some code refactoring that makes the change<br>
easier and possibly improves maintainability of the code. The next two<br>
patches add support for python_check_deps() and python_gen_any_dep()<br>
respectively. The last two patches provide examples for both use cases<br>
mentioned.<br>
<br>
Please review.<br>
<br>
--<br>
Best regards,<br>
Michał Górny<br>
<br>
<br>
</blockquote></div><br></div>



[prev in list] [next in list] [prev in thread] [next in thread]