savannah-hackers
[Top][All Lists]
Advanced

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

Re: [Savannah-hackers] submission of Emacs Packaging Tool - savannah.gnu


From: Rudy Gevaert
Subject: Re: [Savannah-hackers] submission of Emacs Packaging Tool - savannah.gnu.org
Date: Wed, 16 Apr 2003 05:33:36 -0400
User-agent: Mutt/1.3.28i

Hi,

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

On Tue, Apr 15, 2003 at 08:34:24PM -0400, address@hidden wrote:
> 
> A package was submitted to savannah.gnu.org
> This mail was sent to address@hidden, address@hidden
> 
> 
> Jose E. Marchesi <address@hidden> described the package as follows:
> License: gpl
> Other License: 
> Package: Emacs Packaging Tool
> System name: ept
> Type: GNU
> 
> Description:
> EPT intend to be an (GNU) Emacs Packaging Tool.
> 
> The goal is to set up a full featured GNU Emacs packaging
> infrastructure, with two main objetives:
> 
> * An easy maintaining of a per-user local 
>   emacs-site (at ~/emacs-site), instead of 
>   usually chaotic ~/myemacs directory present
>   in hundred of home directories in the world :)
> 
> * Make the installation of the several elisp
>   extensions more easy. This will enhance the
>   sharing of these extensions (W3, erc, tramp, etc).
> 
> EPT is highly inspired in Debian\'s apt packaging tool. 
> All files (includying the .epk packages and the databases)
> are written in elisp. This includes version management and
> support for several remote sources for packages (ftp, http, ...)
> 
> 
> Other Software Required:
> Any Emacs flavor (it is preferible GNU Emacs :)
> 
> Other Comments:
> There are some code already written, so i am able to 
> do M-xept-search and M-xept-update 

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.


Rudy
-- 
Rudy Gevaert                address@hidden              
Web page                    http:/www.webworm.org
GNU/Linux for schools       http://www.nongnu.org/glms
Savannah hacker             http://savannah.gnu.org
                                        




reply via email to

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