From: Tim Van den Langenbergh <tmt_vdl@gmx.com>
To: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
Cc: guile-user@gnu.org
Subject: Re: guile-hall issues converting my project to a hall project
Date: Tue, 16 Feb 2021 17:48:20 +0100 [thread overview]
Message-ID: <6330005.mNMjihpRT5@terra> (raw)
In-Reply-To: <02902ff9-1585-a453-4e36-c9a731eee6fe@posteo.de>
Err, looking at your hall.scm file, you have the fslib file added to your
libraries twice.
Guix environment is not needed if you have all the requirements for building
the package installed locally, but if you want to distribute your package it's
good practise to ensure it builds in a clean environment (see also https://
guix.gnu.org/manual/en/html_node/Invoking-guix-environment.html for more
information about Guix environments).
The "COPYING" file is hardcoded as license file in Hall, to ensure compatibility
with GNU standards: https://www.gnu.org/licenses/gpl-howto.en.html
Hope this helps,
Vale
-Tim
next prev parent reply other threads:[~2021-02-16 16:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-06 21:49 guile-hall issues converting my project to a hall project Zelphir Kaltstahl
2021-02-07 9:14 ` tomas
2021-02-07 13:30 ` Tim Van den Langenbergh
2021-02-11 20:30 ` Zelphir Kaltstahl
2021-02-16 0:23 ` Zelphir Kaltstahl
2021-02-17 22:47 ` Vladimir Zhbanov
2021-02-18 12:18 ` alex sassmannshausen
[not found] ` <11206998.46ALo4VoAQ@terra>
[not found] ` <02902ff9-1585-a453-4e36-c9a731eee6fe@posteo.de>
2021-02-16 16:48 ` Tim Van den Langenbergh [this message]
2021-02-16 18:12 ` Zelphir Kaltstahl
2021-02-17 21:17 ` Alex Sassmannshausen
2021-02-18 19:16 ` Zelphir Kaltstahl
2021-02-21 13:42 ` Alex Sassmannshausen
2021-02-22 11:34 ` guile-hall packaging guide Zelphir Kaltstahl
2021-02-22 20:52 ` Jérémy Korwin-Zmijowski
2021-02-23 16:32 ` Alex Sassmannshausen
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6330005.mNMjihpRT5@terra \
--to=tmt_vdl@gmx.com \
--cc=guile-user@gnu.org \
--cc=zelphirkaltstahl@posteo.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).