unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: zimoun <zimon.toutoune@gmail.com>,
	"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: 57581@debbugs.gnu.org, Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: bug#57581: Failing to build the website
Date: Wed, 07 Sep 2022 19:14:28 +0200	[thread overview]
Message-ID: <F3F3E6E2-AE1A-47DD-8BB3-7E9A6C137A08@lepiller.eu> (raw)
In-Reply-To: <86y1uvxge9.fsf@gmail.com>



Le 7 septembre 2022 19:07:10 GMT+02:00, zimoun <zimon.toutoune@gmail.com> a écrit :
>Hi,
>
>Well, the field reads,
>
>+    (license (package-home-page qtbase))))
>
>so why is the compiler accepting that?  Is a warning raised?
>

No warning because the compiler has no way to know you don't want to do that. license is a field, and fields don't have a specific type except for convention.

package-home-page will read a field from another object, return a perfectly valid Scgeme object (a string) and Scheme is happy to put it in the license field. Why would it care? (:

It fails much later when something tries to read the license field and gets a string it treats as a license object.




  reply	other threads:[~2022-09-07 17:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-04 15:18 bug#57581: Failing to build the website Julien Lepiller
2022-09-05  8:35 ` zimoun
2022-09-05 10:27   ` Julien Lepiller
2022-09-05 11:57     ` zimoun
2022-09-05 10:59   ` pelzflorian (Florian Pelz)
2022-09-05 12:04     ` zimoun
2022-09-05 12:50       ` Julien Lepiller
2022-09-05 14:35 ` zimoun
2022-09-07 16:31   ` pelzflorian (Florian Pelz)
2022-09-07 17:07     ` zimoun
2022-09-07 17:14       ` Julien Lepiller [this message]
2022-09-08  8:00         ` zimoun
2022-09-13 14:41     ` Ludovic Courtès
2022-09-14  6:37       ` zimoun

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=F3F3E6E2-AE1A-47DD-8BB3-7E9A6C137A08@lepiller.eu \
    --to=julien@lepiller.eu \
    --cc=57581@debbugs.gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    --cc=pelzflorian@pelzflorian.de \
    --cc=zimon.toutoune@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).