From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Lars-Dominik Braun <lars@6xq.net>
Cc: Tanguy Le Carrour <tanguy@bioneland.org>,
Munyoki Kilyungi <me@bonfacemunyoki.com>,
74582@debbugs.gnu.org, jgart <jgart@dismail.de>,
Marius Bakke <marius@gnu.org>,
Sharlatan Hellseher <sharlatanus@gmail.com>
Subject: [bug#74582] [PATCH python-team 1/4] build/pyproject: Really merge directories in install phase.
Date: Sun, 15 Dec 2024 00:12:58 +0900 [thread overview]
Message-ID: <87v7vm1eo5.fsf@gmail.com> (raw)
In-Reply-To: <Z0lsD5JDyxEAGlEr@noor.fritz.box> (Lars-Dominik Braun's message of "Fri, 29 Nov 2024 08:23:59 +0100")
Hi,
Lars-Dominik Braun <lars@6xq.net> writes:
> Hi,
>
>> + ;; Use 'copy-recursively' rather than 'rename-file' to guard
>> + ;; against the odd case where DESTINATION is a non-empty
>> + ;; directory, which may happen when using hybrid Python
>> + ;; build systems.
>> + (copy-recursively (string-append source "/" file)
>> + (string-append destination "/" file))
>> + (delete-file-recursively (string-append source "/" file))
>
> wouldn’t it be easier to remove this function entirely and move the
> shebang-replacement via POST-MOVE into a separate function (perhaps
> powered by FIND-FILES instead of SCANDIR)?
Yes, that could be nicer. I'd like to keep it for a distinct commti
though, to keep this small and focus.
> I believe with this patch we can also remove &cannot-extract-multiple-wheels
> further down, since directories should be merged now, right?
Perhaps, though we'd want to verify that it indeed now works, and not
having seen that error once, I'm not too sure how to test it. Do you
know of a package that could make use of this?
--
Thanks,
Maxim
next prev parent reply other threads:[~2024-12-14 15:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-28 8:05 [bug#74582] [PATCH python-team 0/4] Fix edge case in pyproject-build-system Maxim Cournoyer
2024-11-28 12:16 ` [bug#74582] [PATCH python-team 1/4] build/pyproject: Really merge directories in install phase Maxim Cournoyer
2024-11-29 7:23 ` Lars-Dominik Braun
2024-12-14 15:12 ` Maxim Cournoyer [this message]
2024-12-15 16:25 ` Lars-Dominik Braun
2024-11-28 12:16 ` [bug#74582] [PATCH python-team 2/4] build/pyproject: Fix indentation Maxim Cournoyer
2024-11-28 12:16 ` [bug#74582] [PATCH python-team 3/4] build/pyproject: Update PEP 427 reference URL in comment Maxim Cournoyer
2024-11-28 12:16 ` [bug#74582] [PATCH python-team 4/4] build/pyproject: Resolve import warning Maxim Cournoyer
2024-11-28 18:44 ` jgart via Guix-patches via
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v7vm1eo5.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=74582@debbugs.gnu.org \
--cc=jgart@dismail.de \
--cc=lars@6xq.net \
--cc=marius@gnu.org \
--cc=me@bonfacemunyoki.com \
--cc=sharlatanus@gmail.com \
--cc=tanguy@bioneland.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).