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

[Rudy Gevaert]

Hi,

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

On Thu, Jan 23, 2003 at 07:47:32PM -0500, address@hidden wrote:
> 
> A package was submitted to savannah.nongnu.org
> This mail was sent to address@hidden, address@hidden
> 
> 
> Jack Smith <address@hidden> described the package as follows:
> License: gpl
> Other License: 
> Package: Linux Installer

"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


> System name: guinstaller
> Type: non-GNU
> 
> Description:
> A Gtk+ based installation program to assist the people who are in fear 
> of the command line. It is written using GLADE in C. It currently 
> support .tar.gz, .tar.bz2, .tar.Z and basic rpm support. It untars and 
> unzips the file and runs ./configure, make and make install. I am currently 
> trying to add support for an \"uninstall\" feature.
> 
> The source code could be downloaded from 
> 
> http://prdownloads.sourceforge.net/guinstaller/guinstaller-0.4.0.tar.gz?download

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

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,

Rudy