public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: James Le Cuirot <chewi@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH] Eclass changes for cross-compiling Python modules
Date: Sat, 5 Jan 2019 00:06:52 +0000	[thread overview]
Message-ID: <20190105000652.3436040f@symphony.aura-online.co.uk> (raw)
In-Reply-To: <1546617822.1895.12.camel@gentoo.org>

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

On Fri, 04 Jan 2019 17:03:42 +0100
Michał Górny <mgorny@gentoo.org> wrote:

> On Thu, 2019-01-03 at 21:39 +0000, James Le Cuirot wrote:
> > Here's a series of eclass changes I've been working on since August to
> > allow Python modules to be cross-compiled. We previously believed this
> > to be practically impossible without significant changes upstream and
> > in the wider Python ecosystem so getting here feels like quite an
> > achievement. While the approach is a little unconventional, it doesn't
> > feel overly hacky and the results are quite consistently good.
> > 
> > These changes should also benefit prefix and I did a full prefix
> > bootstrap for the first time this week just to make sure I didn't
> > break it.
> > 
> > A handful of other Python packages that don't quite follow the usual
> > mantra have needed fixing up. I haven't included those changes here
> > but you can view them on this GitHub pull request.
> > 
> > https://github.com/gentoo/gentoo/pull/9822
> > 
> > Once this is in place, I can finish my long-awaited revamp of my
> > cross-boss project that will allow you to cross-compile @system from
> > scratch with very little effort.
> >   
> 
> I've reviewed a few commits but I think I had enough.  If you really
> want to push this forward, please start by merging fixes into your
> previous commits because it's really not useful to have commits like
> 'fix bugs in commit 3 you've already reviewed'.

Sure, that's what I usually do.

> Then, you should seriously think how to make things simple.  Because
> the eclass is very complex right now, and doubling the complexity for
> the sake of corner case of cross isn't going work for me.  The last
> thing we need is more hacks on top of hacks to work around previous
> hacks.

I knew this was going to be a tough sell and I put it up on GitHub
first to get your initial feedback and keep you in the loop. Of course
I want to keep it simple, not least so it has a greater chance of being
accepted, but you should know better than most that this was never
going to be easy. As I said, we initially thought it was impossible.
I'll respond to your points so far on the list but we can take this
back to GitHub to avoid spamming everyone else.

-- 
James Le Cuirot (chewi)
Gentoo Linux Developer

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

      reply	other threads:[~2019-01-05  0:07 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-03 21:39 [gentoo-dev] [PATCH] Eclass changes for cross-compiling Python modules James Le Cuirot
2019-01-03 21:39 ` [gentoo-dev] [PATCH 01/12] python-utils-r1.eclass: Fix some double slash paths James Le Cuirot
2019-01-03 21:39 ` [gentoo-dev] [PATCH 02/12] python-utils-r1.eclass: New python_fix_shebang approach James Le Cuirot
2019-01-04  6:02   ` Michał Górny
2019-01-06 17:20     ` James Le Cuirot
2019-01-03 21:39 ` [gentoo-dev] [PATCH 03/12] python-utils-r1.eclass: Have wrapper workdir default to "impl" arg James Le Cuirot
2019-01-03 21:39 ` [gentoo-dev] [PATCH 04/12] python-utils-r1.eclass: Use wrapper scripts to fix cross-compiling James Le Cuirot
2019-01-04 15:53   ` Michał Górny
2019-01-05 21:30     ` James Le Cuirot
2019-01-03 21:39 ` [gentoo-dev] [PATCH 05/12] python-utils-r1.eclass: Replace temporary paths in python_fix_shebang James Le Cuirot
2019-01-03 21:39 ` [gentoo-dev] [PATCH 06/12] python-utils-r1.eclass: Don't die in python_fix_shebang if all fixed James Le Cuirot
2019-01-04 15:55   ` Michał Górny
2019-01-04 18:10     ` Mike Gilbert
2019-01-04 18:26       ` Michał Górny
2019-01-05 21:38         ` James Le Cuirot
2019-01-05 21:42           ` Michał Górny
2019-01-06 14:52             ` James Le Cuirot
2019-01-03 21:39 ` [gentoo-dev] [PATCH 07/12] python-utils-r1.eclass: Add special wrapper handling for Python itself James Le Cuirot
2019-01-03 21:39 ` [gentoo-dev] [PATCH 08/12] python-utils-r1.eclass: Adjust wrappers for Python 3.7 libdir change James Le Cuirot
2019-01-03 21:39 ` [gentoo-dev] [PATCH 09/12] python-any-r1.eclass: Export PYTHON after checking whether installed James Le Cuirot
2019-01-03 21:39 ` [gentoo-dev] [PATCH 10/12] python-any-r1.eclass: Create wrappers against build system's config James Le Cuirot
2019-01-03 21:39 ` [gentoo-dev] [PATCH 11/12] distutils-r1.eclass: Fix cross-compiling James Le Cuirot
2019-01-03 21:39 ` [gentoo-dev] [PATCH 12/12] distutils-r1.eclass: Make distutils-r1_create_setup_cfg external James Le Cuirot
2019-01-04  2:11 ` [gentoo-dev] [PATCH] Eclass changes for cross-compiling Python modules Benda Xu
2019-01-04 16:03 ` Michał Górny
2019-01-05  0:06   ` James Le Cuirot [this message]

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=20190105000652.3436040f@symphony.aura-online.co.uk \
    --to=chewi@gentoo.org \
    --cc=gentoo-dev@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