> Could you check your other Savannah-hosted packages for such omissions?

Sure, over the next several weeks (sooner or later).

Thanks for your help.

Happy hacking!

> It's a text file; why doesn't it permit comments?

It's actually a binary format (note magic numbers and ^_ throughout) w/ a large textual component.  I've described this...

> And even if it didn't, the notices should be added in a README file in the same directory with the files in question.

...in the new doc/README file, per your suggestion.  Thanks!  Here's the doc/README in its entirety:

| This directory contains documentation for Guile-BAUX.
|
| The primary format is Info -- use "make info" or "make" to build it.
| You can also obtain PDF output w/ command "make pdf".
|
| The documentation source file guile-baux.texi has its own copyright notice.
| Most other source files are too small to have their own notice.  One notable
| exception is the file "snippets", which is in "texinfo snippet archive"
| format (info "(guile-baux) ts-base").  Because it's a binary format file,
| it doesn't have a comment syntax that supports adding a copyright notice.
| Furthermore, it is generated by scanning actual source files, so if anything
| it should fall under the following copyright notice:
|
|  Copyright (C) 2010-2020 Thien-Thi Nguyen
|
|  Copying and distribution of this file, with or without modification,
|  are permitted provided the copyright notice and this notice are preserved.
|
| which you will note is the same copyright notice as this README file.  Ah,
| congruence!  :-D
|
| 
| Copyright (C) 2010-2020 Thien-Thi Nguyen
|
| Copying and distribution of this file, with or without modification,
| are permitted provided the copyright notice and this notice are preserved.

That file is a "texinfo snippet archive", akin to ".tar" format.  IOW, its format does not permit comments aside from the first line , so adding a copyright notice is not feasible.

Anyway, that is a generated file; it is remade if you should touch any of the source files and then do "make".  It is distributed in the spirit of documentation: possible to regenerate, but not necessary, so we distribute it as a convenience to the user.

OK, please find attached lzipped tarball.


(file #48293)

Thanks for the quick review.  I have added a copyright notice to README and updated the years for a few other files.  Here is the copyright notice for the README:

Copyright (C) 2010, 2017, 2020 Thien-Thi Nguyen

Copying and distribution of this file, with or without modification,
are permitted provided the copyright notice and this notice are preserved.

If you would like, i can upload a new tarball (116KB).

A new project has been registered at Savannah
This project account will remain inactive until a site admin approves
or discards the registration.

Registration Administration

While this item will be useful to track the registration process,
approving or discarding the registration must be done using the specific Group Administration page, accessible only to site administrators,
effectively logged as site administrators (superuser):

• Group Administration

Registration Details

• Name: Guile-BAUX
• System Name:  guile-baux
• Type: non-GNU software and documentation
• License: GNU General Public License v3 or later (The item "my tarball includes a copy of the license" is not exactly correct since the project functions like GNU gnulib -- no release tarballs.  However, the repo does indeed contain a COPYING file (GPLv3) so that's why this item is checked off -- it follows the spirit of the item.

The item "origin and license of media files is specified" is checked-off even though there are no media files in this project.)

---

Description:

Guile-BAUX is a set of Guile Scheme modules (some of them functioning as programs executable from the command-line) aimed towards easing the maintenance of Guile-related projects.  This includes areas such as:

- documentation extraction/organization/generation
- dependency (between modules) computations
- extraction of ".x" info for C-language integration
- support for "two-layer" (C + Scheme) modules
- etc

It does this while itself maintaining compatibility w/ Guile versions from 1.4 and up, and operating much like GNU gnulib (copying files into the package, no fixed releases, etc).

Guile-BAUX is currently used in every Guile-related package that I maintain, including GNU Guile-SDL, GNU Alive, Mixp, Guile-PG, Guile-WWW, and so on.

Until now I've maintained it in private, but recently, a needed change to Mixp showed that this important piece of maintenance functionality should be public, in order to guarantee proper succession in case of ttn bus error...

Other Software Required:

- GNU Guile (http://www.gnu.org/software/guile)

Tarball URL:

https://savannah.gnu.org/submissions_uploads/guile-baux.tar.gz