From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Nigko Yerden <nigko.yerden@gmail.com>
Cc: Attila Lendvai <attila@lendvai.name>, guix-devel@gnu.org
Subject: Re: Cookbook recipe from "The Repository as a Channel" section does not work for Guix with properly configured GUILE_LOAD_PATH
Date: Mon, 26 Aug 2024 10:50:45 +0200 [thread overview]
Message-ID: <87le0jsm56.fsf@pelzflorian.de> (raw)
In-Reply-To: <00be7dd1-ca5f-48a2-b89f-acb9f0d9c69f@gmail.com> (Nigko Yerden's message of "Sat, 24 Aug 2024 19:47:59 +0500")
Hello Nigko.
Nigko Yerden <nigko.yerden@gmail.com> writes:
> pelzflorian (Florian Pelz) wrote:
>> If the configuration or package file is not in the load-path,
>> guile-package.scm is returned, absolute-dirname’s other `if' branch
>> calls `canonicalize-path' on all but the basename and directory symlinks
>> already got resolved.
> No, in this case 'search-path' returns #f. But if 'syntax-source' gives
> absolute path, then 'current-source-directory' returns 'dirname' of this
> path without calling 'absolute-dirname'.
Oops. Indeed, your view is right.
Still, when would your diff break someone else’s code?
They would need to currently use `local-file' or `current-source-directory'
to reference a file in .config/guix/current/share/guile/site/3.0,
which your diff would break. But this still seems unlikely to me.
What `local-file' needs is a kind of current-source-directory.
Current `current-source-directory' does a bad job in channels. Your
diff does fix this. The compatibility burden is on the channel
authors. `current-source-directory' would no longer be bad in what we
deem realistic use.
Regards,
Florian
next prev parent reply other threads:[~2024-08-26 8:51 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-13 12:45 Cookbook recipe from "The Repository as a Channel" section does not work for Guix with properly configured GUILE_LOAD_PATH Nigko Yerden
2024-08-13 14:38 ` pelzflorian (Florian Pelz)
2024-08-13 15:06 ` Nigko Yerden
2024-08-13 17:25 ` pelzflorian (Florian Pelz)
2024-08-13 17:49 ` Nigko Yerden
2024-08-14 15:35 ` pelzflorian (Florian Pelz)
2024-08-14 16:40 ` pelzflorian (Florian Pelz)
2024-08-14 19:29 ` pelzflorian (Florian Pelz)
2024-08-15 4:11 ` Nigko Yerden
2024-08-18 21:33 ` pelzflorian (Florian Pelz)
2024-08-19 7:43 ` Nigko Yerden
2024-08-19 19:28 ` pelzflorian (Florian Pelz)
2024-08-20 7:18 ` Nigko Yerden
2024-08-20 16:49 ` pelzflorian (Florian Pelz)
2024-08-22 4:45 ` pelzflorian (Florian Pelz)
2024-08-22 9:53 ` Nigko Yerden
2024-08-22 13:22 ` Nigko Yerden
2024-08-22 16:00 ` pelzflorian (Florian Pelz)
2024-08-23 5:07 ` Nigko Yerden
2024-08-23 15:47 ` pelzflorian (Florian Pelz)
2024-08-23 16:25 ` pelzflorian (Florian Pelz)
2024-08-24 14:47 ` Nigko Yerden
2024-08-26 8:50 ` pelzflorian (Florian Pelz) [this message]
2024-08-28 12:36 ` Nigko Yerden
2024-08-28 16:40 ` pelzflorian (Florian Pelz)
2024-08-29 6:17 ` Nigko Yerden
2024-08-19 9:30 ` Nigko Yerden
2024-08-19 16:17 ` Nigko Yerden
2024-08-14 14:00 ` Attila Lendvai
2024-08-15 16:34 ` Nigko Yerden
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=87le0jsm56.fsf@pelzflorian.de \
--to=pelzflorian@pelzflorian.de \
--cc=attila@lendvai.name \
--cc=guix-devel@gnu.org \
--cc=nigko.yerden@gmail.com \
/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).