1
- #+TITLE: Common Lisp Package Manager - CLPM
1
+ #+TITLE: Common Lisp Project Manager - CLPM
2
2
#+AUTHOR: Eric Timmons
3
3
4
4
#+OPTIONS: email:t toc:1 num:nil
@@ -14,8 +14,10 @@ appropriate tag or see [[http://www.clpm.dev]].
14
14
15
15
* Description
16
16
17
- CLPM is a package manager for Common Lisp. It can manage packages in both
18
- global and project specific contexts.
17
+ CLPM is a project manager for Common Lisp. It can manage projects in both
18
+ global and project specific contexts. It would be called a "package manager"
19
+ in most other contexts, but the use of "package" unfortunately collides with
20
+ the use of "package" in the Common Lisp spec as a namespace for symbols.
19
21
20
22
It consists of two major pieces. First is a standalone program that is
21
23
responsible for all the heavy lifting of downloading and unpacking releases
@@ -153,7 +155,7 @@ appropriate tag or see [[http://www.clpm.dev]].
153
155
154
156
* Project Goals
155
157
156
- CLPM is far from the only package manager available for Common Lisp[fn:1], but
158
+ CLPM is far from the only project manager available for Common Lisp[fn:1], but
157
159
it makes very different assumptions and design choices than the other
158
160
available solutions. In this section we describe our high level goals and how
159
161
they affect our design decisions.
@@ -168,8 +170,8 @@ appropriate tag or see [[http://www.clpm.dev]].
168
170
code the Quicklisp client depends on and the code you're developing depends
169
171
on, and it helps ensure that Quicklisp works on a broad set of Common Lisp
170
172
implementations. However, it has a major downside: the maintenance and
171
- development costs of the package manager are high, potentially making it
172
- difficult to implement new features and the package manager does not really
173
+ development costs of the project manager are high, potentially making it
174
+ difficult to implement new features and the project manager does not really
173
175
drive the quality of code in the community at large higher.
174
176
175
177
The desire to use existing libraries drives the decision for the CLPM core
@@ -202,8 +204,8 @@ appropriate tag or see [[http://www.clpm.dev]].
202
204
203
205
Many Common Lisp implementations allow you to deliver programs by dumping an
204
206
image to file. For most programs generated this way there is no need to have
205
- a bundled package manager. Therefore, there should be an easy way to use a
206
- package manager without leaving traces if it in your deployed system.
207
+ a bundled project manager. Therefore, there should be an easy way to use a
208
+ project manager without leaving traces if it in your deployed system.
207
209
208
210
To this end, CLPM can be used without ever loading the client (for example,
209
211
=clpm bundle exec= configures ASDF entirely through environment variables)
0 commit comments