[lispy-devel] Packages versus systems

[Matthew Kennedy]

On Wed, Apr 2, 2008 at 5:39 AM, Michael Ben-Yosef <septagon at mweb.co.za> wrote:

>
>  I would like to make a recommendation with regard to the terminology that
> is being used. I strongly suggest calling it a "system manager" for Common
> Lisp instead of a "package manager". As you know, the word "package" already
> has a very specific meaning in the CL language. The fact that a package in

I agree that the package terminology I've used is unfortunate and
should be changed.  How about if we refer to Lispy dowloading
**libraries** and managing **systems**?

So the changes on the project page would look like this:

Common Lisp **system** management in Common Lisp...
Lispy is a **system** manager for Common Lisp, written in Common Lisp...
1. Implement an easy to use, portable **system** manager...
2. Provide a wealth of ready to install **libraries**...
new releases and also new **libraries** available in the maps...
Lispy uses distributed software maps to locate Common Lisp **libraries**...
You may have your own **libraries** or other **libraries** not...
All Common Lisp **libraries** mapped...
These **library** archives are modified...
The **library** archive lacks a version number...
The **library** needs to be patched

In Lispy's source and also the map files themselves, I've used
"module" where I really mean "library".  I think I will change module
to library for the next release and update all the maps in a backwards
compatible manner.

Matt