savannah-hackers
[Top][All Lists]
Advanced

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

[Savannah-hackers] Re: submission of Mongoose Free OS Distribution Syst


From: Mathieu Roy
Subject: [Savannah-hackers] Re: submission of Mongoose Free OS Distribution System - savannah.gnu.org
Date: 04 May 2003 13:52:44 +0200
User-agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2

Hi,

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



address@hidden said:

> A package was submitted to savannah.gnu.org
> This mail was sent to address@hidden, address@hidden
> 
> Peter Gavin <address@hidden> described the package as follows:
> License: gpl
> Other License: 
> Package: Mongoose Free OS Distribution System
> System name: mongoose
> Type: GNU
> 
> Description:
> The purpose of this project is to create a 100% architecture and kernel 
> independent meta-distribution. Basically, this will consist of a package 
> manager, which I am calling Mpak, and a set of packages. Mpak will also be 
> distribution independent, like RPM. Mpak will be able to calculate and 
> automatically be able to build dependencies for all packages, and will have 
> support for bootstrapping dependency cycles. It will also have support for 
> specifying any features you want compiled into the package, both globally and 
> on a per package basis. Many other features are planned!

Note that on Savannah we can only host mpak, the distribution tool,
not the distribution in itself (packages). 

> 
> I have some beginning C++ code I\'ve written for Mpak, which once I
> clean up, I will put into CVS.

Please register your project again including a URL
(could be temporary) where we can find the source code.
The description you give during project registration will be
read by Savannah administrators and not by the general public;
if you are concerned with privacy, you can
send me a copy of the code by e-mail,

We would like to look at your source code, even if it is still
not functional, to help you fix potential legal issues which
would be harder to correct after the project gets approved.
For example, to release your program properly under the GPL,
you should write copyright notices and copying permission statements
at the beginning of every source code file,
as explained in http://www.gnu.org/licenses/gpl-howto.html.

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




reply via email to

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