[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Savannah-register-public] [task #15279] Submission of Gash: Guile as Sh

From: Timothy Sample
Subject: [Savannah-register-public] [task #15279] Submission of Gash: Guile as Shell
Date: Tue, 21 May 2019 12:48:18 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0

Follow-up Comment #2, task #15279 (project administration):

Thanks for the quick review!

Sorry for missing the notice in README. Guix and Guile omit it, and they were
among the packages that I was using for examples. I will put a notice at the
bottom, like in Bash.

I searched for all the files missing the word "copyright", and came up with
the following. Most of them are omissions that I can fix easily, but I would
appreciate some advice for a few.

*Guile Rules*

I'm having a hard time tracking the provenance of the build-aux/
file. The same text exists in basically all Guile projects, and many of them
have different notices. I honestly cannot say which projects I based this file
on anymore (I looked at quite a few and synthesized them). My best idea is to
pick a reasonable source (like Guix or 8sync) and use that notice. Is that


There are 199 tiny test files. Bash handles this by a special COPYRIGHT file
that covers all the tests. Can I do the same?


I would argue that these files are "trivial". However, if you disagree, please
let me know and I will add a notice.

* ChangeLog
* .dir-locals.el
* .gitignore (only in the Git repository)


I know the authorship and licenses of these files, and can add a notice

* build-aux/gitlab-ci.yml
* build-aux/
* doc/syntax.txt
* guix.scm
* tests/spec/check-spec
* tests/spec/

Let me know what you think, and then I will prepare a new tarball following
your suggestions.

Thanks again!


Reply to this item at:


  Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]