[Savannah-hackers] Re: submission of Tiny Configuration File Library - savannah.nongnu.org

[Mathieu Roy]

Hi,

I'm evaluating the project you submitted for approval in Savannah.



address@hidden said:

> A package was submitted to savannah.nongnu.org
> This mail was sent to address@hidden, address@hidden
> 
> Rodolphe Saugier <address@hidden> described the package as follows:
> License: lgpl
> Other License: 
> Package: Tiny Configuration File Library
> System name: tinycfgfile
> Type: non-GNU
> 
> Description:
> This is a tiny multiplatform C library to read/write simple configuration 
> files. It only depends on basic libc functionalities.
> 
> The configuration file is a text file with each line following this format:
> 
> <keyname> = <value>
> 
> where <keyname> is an identifier, and <value> is a literal constant that may 
> be:
> 
>  - An integer
> 
>  - A float 
> 
>  - A string (with partial support for C-like syntax)
> 
> Comments are also accepted (prefixed by ';').
> 
> The contents of the config file are not kept into memory (the file is always 
> the reference). The library is intended to be kept extremely simple, so that 
> *any* C program would be able to reuse it.
> 
> Goals:
> 
>  - Small size (memory consumption).
> 
>  - Portability (standard C compliance).
> 
>  - As few dependencies as possible.
> 
>  - Reusability.
> 
>  - 100% reliability (Unit tests should be written)
> 
>  - That no one ever reinvents such a thing again ;) (ok, maybe I'm the fool 
> ;o) (but... why everybody's laughing at me???)
> 
> Very preliminary source code URL: 
> http://rolf1.free.fr/dnload/configfile.tar.gz

To release your project under the GPL, you should put
copyright notices and copying permission statements
at the beginning of every source-code file, and
include a copy of the plain text version of the GPL
(http://www.gnu.org/licenses/gpl.txt).
Put it in a file named COPYING.

Please follow the advice of http://www.gnu.org/licenses/gpl-howto.html.

The GPL FAQ explain the reason behind these recommendations.  For
example, there is an entry explaining why the GPL requires including a
copy of the GPL with every copy of the program:
 http://www.gnu.org/licenses/gpl-faq.html#WhyMustIInclude


Please register your project once more with the changes mentioned
above.  The way we handle pending projects makes it difficult to keep
track of projects that have been answered but have not been approved
yet, so we erase them and we ask you to register the project again every
time some change has to be done to the registration, and users might
have to register their projects several times.  Thank you for your
understanding.

Some users find it useful to use the big re-registration URL provided in
the acknowledgment e-mail you received after registration.

Regards,


-- 
Mathieu Roy
 
  Homepage:
    http://yeupou.coleumes.org
  Not a native english speaker: 
    http://stock.coleumes.org/doc.php?i=/misc-files/flawed-english