From: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
To: Tim Van den Langenbergh <tmt_vdl@gmx.com>
Cc: guile-user@gnu.org
Subject: Re: guile-hall issues converting my project to a hall project
Date: Tue, 16 Feb 2021 19:12:04 +0100 [thread overview]
Message-ID: <fc8533a5-9f30-61c7-f893-0775dc4b5c5b@posteo.de> (raw)
In-Reply-To: <6330005.mNMjihpRT5@terra>
Hello Tim!
Thank you, it works now!
Removing the duplicate entry of `fslib` in hall.scm fixed it.
Regarding the license: OK, I have no problem moving my license to
`COPYING`. However, I still think, that it should not put GPL there,
when I specified AGPL in `hall.scm`. This looks like a hardcoded
fallback, which does not take the license specification into account.
Something like: "If there is no `COPYING` file just put GPL into a file
`COPYING`." instead of "If there is no `COPYING` file just put
<user-specified-license-in-hall.scm> into a file `COPYING`.". I could be
wrong though, as I do not know anything about guile-hall's internals.
Follow up question would be, how to bring the package into the guix
repository, but I am guessing, that it will be answered at
https://guix.gnu.org/cookbook/en/html_node/Direct-checkout-hacking.html,
which I have not read yet.
Another question is, whether I should put you into the authors file and
write something like "help with packaging" there. What is the common
practice?
Best regards,
Zelphir
On 2/16/21 5:48 PM, Tim Van den Langenbergh wrote:
> 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
>
>
--
repositories: https://notabug.org/ZelphirKaltstahl
next prev parent reply other threads:[~2021-02-16 18:12 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
2021-02-16 18:12 ` Zelphir Kaltstahl [this message]
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=fc8533a5-9f30-61c7-f893-0775dc4b5c5b@posteo.de \
--to=zelphirkaltstahl@posteo.de \
--cc=guile-user@gnu.org \
--cc=tmt_vdl@gmx.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.
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).