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
