savannah-hackers
[Top][All Lists]
Advanced

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

[Savannah-hackers] Re: submission of libconf - savannah.nongnu.org


From: Mathieu Roy
Subject: [Savannah-hackers] Re: submission of libconf - savannah.nongnu.org
Date: 11 Nov 2002 17:12:26 +0100
User-agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2

Hi,

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

Please, accept our apologizes for the delay,

address@hidden said:

> A package was submitted to savannah.nongnu.org
> This mail was sent to address@hidden, address@hidden
> 
> charly <address@hidden> described the package as follows:
> License: gpl
> Other License: 
> Package: libconf
> System name: libconf
> Type: non-GNU
> 
> Description:
> When a program wants to ease the configuration of the linux system, it has to 
> edit some configuration files. But parsing a file is not always easy, when it 
> has to deal with complex syntax, or (nested) comments, redondant 
> informations...
> 
> libconf provides the functions to read, modify, and check any configuration 
> files, provided that it has the appropriated template and validation data.
> libconf is written in perl, but will be able to interface with multiple 
> language and document format, like xml. 
> 
> There\'s a more detailed description here :
> http://gentoo.org/doc/libconf.html
> 
> There\'s doc on libconf template here :
> http://gentoowiki.iq-computing.de/index.php?pagename=libconf%20templates
> 
> There\'s a cvs repository here:
> http://cvsweb.tuxfamily.org/cvs/src/?cvsroot=ugtk
> Access: export CVSROOT=:pserver:address@hidden:/cvsroot/ugtk 
> 

In order to release your project under the GPL you
should write 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 copy it, for
instance, into a file named COPYING).

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


The GPL FAQ can also help you understand the reason behind
thoses 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


Also, "Linux" is just a kernel of a more complex system
that we like to refer to as GNU/Linux, to emphasize
the ideals of the Free Software movement.


Would you mind changing occurences of Linux as OS
to GNU/Linux?

You can get more information at
http://www.gnu.org/gnu/linux-and-gnu.html



-- 
Mathieu Roy
 
 << Profile  << http://savannah.gnu.org/users/yeupou <<
 >> Homepage >> http://yeupou.coleumes.org           >>
 << GPG Key  << http://stock.coleumes.org/gpg        <<




reply via email to

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