From: Adam Faiz <adam.faiz@disroot.org>
To: guix-devel@gnu.org
Subject: (computed-origin-method) and (origin)'s file-name field
Date: Sun, 27 Aug 2023 20:25:48 +0800 [thread overview]
Message-ID: <d169d98a-35ea-715e-d47a-c3bba8d6769c@disroot.org> (raw)
Hello everyone,
I'm wondering about the solution to the computed-origin-method workaround...
Must the 'computed-origin-method' workaround be solved by adding the renaming capability to snippets?
Why couldn't the file-name field of the source origin be used to rename it?
If it's because the upstream source might be confused with the liberated version, couldn't a comment above the snippet clarify that?
next reply other threads:[~2023-08-27 12:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-27 12:25 Adam Faiz [this message]
2023-08-28 12:45 ` (computed-origin-method) and (origin)'s file-name field Simon Tournier
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=d169d98a-35ea-715e-d47a-c3bba8d6769c@disroot.org \
--to=adam.faiz@disroot.org \
--cc=guix-devel@gnu.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).