On 3/9/24 9:32 AM, Michał Górny wrote:
> Hi,
>
> Please consider the "legacy" build mode to be strongly deprecated, both
> in distutils-r1 and upstream (to the point that sole presence of
> packages installed that way triggers deprecation warnings elsewhere,
> sigh). Therefore, if you haven't
On 3/9/24 2:59 PM, Mike Gilbert wrote:
> On Tue, Mar 5, 2024 at 12:16 PM Michał Górny wrote:
>>
>> Make LTO filtering local to the compilation code. This avoids disabling
>> LTO for non-Python parts of an ebuild.
>>
>> Signed-off-by: Michał Górny
>> ---
>> eclass/distutils-r1.eclass | 4
On 3/9/24 4:13 PM, Duncan wrote:
> I'm not saying don't use gentoo -- I'm a gentooer after all -- I'm saying
> gentoo simply isn't in a good position to condemn AI for its energy
> inefficiency. In fact, I'd claim that in the Gentoo case there are
> demonstrably more energy efficient practical
Michał Górny posted on Sat, 09 Mar 2024 16:04:58 +0100 as excerpted:
> On Fri, 2024-03-08 at 03:59 +, Duncan wrote:
>> Robin H. Johnson posted on Tue, 5 Mar 2024 06:12:06 + as excerpted:
>>
>> > The energy waste argument is also one that needs to be made
>> > carefully:
>>
>> Indeed.
On Tue, Mar 5, 2024 at 12:16 PM Michał Górny wrote:
>
> Make LTO filtering local to the compilation code. This avoids disabling
> LTO for non-Python parts of an ebuild.
>
> Signed-off-by: Michał Górny
> ---
> eclass/distutils-r1.eclass | 4
> 1 file changed, 4 insertions(+)
>
> diff --git
On Fri, 2024-03-08 at 03:59 +, Duncan wrote:
> Robin H. Johnson posted on Tue, 5 Mar 2024 06:12:06 + as excerpted:
>
> > The energy waste argument is also one that needs to be made carefully:
>
> Indeed. In a Gentoo context, condemning AI for the computative energy
> waste? Maybe
On Fri, 2024-03-01 at 07:06 +, Sam James wrote:
> Another person approached me after this RFC and asked whether tooling
> restricted to the current repo would be okay. For me, that'd be mostly
> acceptable, given it won't make suggestions based on copyrighted code.
I think an important
On Tue, 2024-02-27 at 18:04 +, Sam James wrote:
> I'm a bit worried this is slightly performative - which is not a dig at
> you at all - given we can't really enforce it, and it requires honesty,
> but that's also not a reason to not try ;)
I don't think it's really possible or feasible to
Hi,
Please consider the "legacy" build mode to be strongly deprecated, both
in distutils-r1 and upstream (to the point that sole presence of
packages installed that way triggers deprecation warnings elsewhere,
sigh). Therefore, if you haven't done that already, please look into
converting your
# Andrew Ammerlaan (2024-03-09)
# Requires pyside2/shiboken2, which is unmaintained upstream and
# not compatible with llvm-16 and up or python-3.12 and up.
# No upstream activity for 2 years.
# dev-python/QtPy is an alternative that does support Qt6.
# Removal on: 2024-04-09. Bug #926548
10 matches
Mail list logo
